From 21ff2c2e276a30b94c4502161c04e3caf886eab1 Mon Sep 17 00:00:00 2001 From: Michael DePouw Date: Tue, 31 Oct 2017 16:42:12 -0400 Subject: [PATCH] fix anchor link to handler registration (#4690) --- aspnetcore/security/authorization/dependencyinjection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/security/authorization/dependencyinjection.md b/aspnetcore/security/authorization/dependencyinjection.md index c594b6c107..d912cedc3f 100644 --- a/aspnetcore/security/authorization/dependencyinjection.md +++ b/aspnetcore/security/authorization/dependencyinjection.md @@ -16,7 +16,7 @@ uid: security/authorization/dependencyinjection -[Authorization handlers must be registered](policies.md#security-authorization-policies-based-handler-registration) in the service collection during configuration (using [dependency injection](../../fundamentals/dependency-injection.md#fundamentals-dependency-injection)). +[Authorization handlers must be registered](policies.md#handler-registration) in the service collection during configuration (using [dependency injection](../../fundamentals/dependency-injection.md#fundamentals-dependency-injection)). Suppose you had a repository of rules you wanted to evaluate inside an authorization handler and that repository was registered in the service collection. Authorization will resolve and inject that into your constructor.