EngineBay.Authentication 2.2.2

EngineBay.Authentication

Authentication module for EngineBay published to EngineBay.Authentication on NuGet.

About

Learn about Authentication and Authorization.

This module provides middleware and services for both authentication and authorization. The behaviour of the authentication depends heavily on your configuration options. The module can be configured to use JWT auth, Basic auth, and no auth. JWT is recommended. The latter two should only be used during local testing - not in a production environment.

Simple endpoints to register a user or get the current user are also provided.

This module also provides implementations of ICurrentIdentity, which can be used by modules such as EngineBay.Auditing, to get information about the current user from the HttpContext.

Not implemented yet: With the authorization middleware, you can specify authorization policies on endpoints to limit access to users with the appropriate permissions.

Usage

When this module is registered and configured, all endpoints will only allow authenticated users by default. To allow unauthenticated users to access an endpoint, you can use the .AllowAnonymous() method on the route builder. For an example, see AuthenticationModule.

Not implemented yet: To restrict access to endpoints to users with specific permissions, you can use .RequireAuthorization("Policy.Name") on the route builder. For an example, see AuditEntryEndpoint.

Registration

This module cannot run on its own. You will need to register it in your application to use its functionality. See the Demo API registration guide.

Since this module uses HttpContextAccessor in custom components, you will need to register it on the service collection for dependency injection. This can be done with the line builder.Services.AddHttpContextAccessor();, as seen here.

Environment Variables

See the Documentation Portal.

Dependencies

• EngineBay.Core
• EngineBay.Persistence