daohualiuxiang
/
AspNetCore.Docs
mirror of https://github.com/dotnet/AspNetCore.Docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Auth handlers - any lifetime (#20309)

pull/20316/head
Rick Anderson 2020-10-27 08:17:16 -10:00 committed by GitHub
parent cc8200296c
commit dfb27d8131
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
aspnetcore/security/authorization/dependencyinjection.md
View File

@ -11,11 +11,11 @@ uid: security/authorization/dependencyinjection
<a name="security-authorization-di"></a>
[Authorization handlers must be registered](xref:security/authorization/policies#handler-registration) in the service collection during configuration (using [dependency injection](xref:fundamentals/dependency-injection)).
[Authorization handlers must be registered](xref:security/authorization/policies#handler-registration) in the service collection during configuration using [dependency injection](xref: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.
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 resolves and injects that into the constructor.
For example, if you wanted to use ASP.NET's logging infrastructure you would want to inject `ILoggerFactory` into your handler. Such a handler might look like:
For example, to use ASP.NET's logging infrastructure, inject `ILoggerFactory` into the handler. Such a handler might look like the following code:
```csharp
public class LoggingAuthorizationHandler : AuthorizationHandler<MyRequirement>
@ -36,13 +36,13 @@ public class LoggingAuthorizationHandler : AuthorizationHandler<MyRequirement>
}
```
You would register the handler with `services.AddSingleton()`:
The preceding handler can be registered with any [service lifetime](/dotnet/core/extensions/dependency-injection#service-lifetimes). The following code uses `AddSingleton` to register the preceding handler:
```csharp
services.AddSingleton<IAuthorizationHandler, LoggingAuthorizationHandler>();
```
An instance of the handler will be created when your application starts, and DI will inject the registered `ILoggerFactory` into your constructor.
An instance of the handler is created when the app starts, and DI injects the registered `ILoggerFactory` into the constructor.
> [!NOTE]
> Handlers that use Entity Framework shouldn't be registered as singletons.