Nice article
tldr;
You can use Fallback Policies in ASP.NET Core 3.0+ to require an Authenticated User by default. Conceptually, you can think of this as adding an [Authorize] attribute by default to every single Controller and Razor Page ONLY WHEN no other attribute is specified on a Controller or Razor Page (like [AllowAnonymous] or [Authorize(PolicyName="PolicyName")]). See lines 9-11 below.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| publicclassStartup |
| { |
| // Other Startup code omitted |
| publicvoidConfigureServices(IServiceCollectionservices) |
| { |
| services.AddAuthorization(options=> |
| { |
| options.FallbackPolicy=newAuthorizationPolicyBuilder() |
| .RequireAuthenticatedUser() |
| .Build(); |
| // Register other policies here |
| }); |
| // Other service registrations omitted |
| } |
| } |
View original post 1,228 more words
Neel Bhatt 
One thought on “Globally Require Authenticated Users By Default Using Fallback Policies in ASP.NET Core”