dotnet-scaffold-auth-policy

Scaffold cross-app authorization policies by defining policy name constants in a shared Security.PolicyNames class and registering them centrally via shared AuthorizationOptionsExtensions, ensuring consistent access control across ASP.NET Core API controllers and Blazor components.

Avoid circular dependencies by defining and registering named authorization policies in a single shared project location, allowing both server and Blazor client code to reference the same centralized policy constants without direct project-to-project dependencies.

Yes, you can apply standard RequireRole and RequireAssertion patterns to Blazor navigation items, API controllers, and Blazor components by referencing shared policy names to enforce specific access boundaries consistently across these application layers.

Register a new authorization policy without duplicating code by adding the policy constant to the shared Security.PolicyNames file and mapping it through the shared AuthorizationOptions extension, enabling predictable and centralized governance of access controls.

Centralize access control policy names when features are added or reorganized and both server API controllers and Blazor client components require consistent policy scoping. Keeping policy names and registration in a single shared location prevents mismatched access boundaries.