ASP.NET Core 8.0 - Cookie Authentication

The authentication configuration defaults should work for most cases as long as the paths to key pages match. The default paths are: LoginPath = "/account/login", LogoutPath = "/account/logout", and AccessDeniedPath = "/account/accessdenied". The CACP implements these paths so there is no need to override these defaults. I do recommend overriding the CookieAuthenticationDefaults. AuthenticationScheme name which is "Cookies". A unique name helps with multiple schemes and debugging multiple projects. The CACP implements a static class named AppSettings.cs for global project settings. The CACP AppSettings. ApplicationScheme = "CACP.Authentication". The CACP implements cookie authentication with just a few lines of code. Setting the Cookie Name removes the .AspNet prefix from the browser's cookie name.

Program.cs:

builder.Services.AddAuthentication()
    .AddCookie(AppSettings.ApplicationScheme, options => { options.Cookie.Name = AppSettings.ApplicationScheme; });

The Authentication middleware is added in Program.cs by calling UseAuthentication. Calling UseAuthentication registers the middleware that uses the previously registered authentication schemes. Call UseAuthentication before any middleware that depends on users being authenticated. See MS - Use cookie authentication without ASP.NET Core Identity.

app.UseAuthentication();

You can override a few more default cookie options but most are superseded by AuthenticationProperties used when the user logs in. See the Remember Me Or Not article.