Dependency Injection in Requirement HandlersΒΆ

As handlers must be registered in the service collection they support dependency injection. If, for example, you had a repository of rules you want to evaluate inside a handler and that repository is registered in the service collection authorization will resolve and inject that into your constructor.

For example, if you wanted to use ASP.NET’s logging infrastructure you would to inject ILoggerFactory into your handler. Such a handler might look like this;

public class LoggingAuthorizationHandler : AuthorizationHandler<MyRequirement>
    ILogger _logger;

    public LoggingAuthorizationHandler(ILoggerFactory loggerFactory)
        _logger = loggerFactory.CreateLogger(this.GetType().FullName);

    protected override Task HandleRequirementAsync(AuthorizationHandlerContext context, MyRequirement requirement)
        _logger.LogInformation("Inside my handler");
        // Check if the requirement is fulfilled.
        return Task.CompletedTask;

Then you register handlers with services.AddSingleton(), for example

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.