How jasontaylordev/flexible-aspnetcore-authorization works
Project type and purpose
• This is a full-stack ASP.NET Core sample application demonstrating two authorization approaches: “BasicAuth” for simple role-based auth and “FlexibleAuth” for fine-grained, permission-based policies.
• It uses Blazor WebAssembly for the client, an ASP.NET Core Web API with Identity (Entity Framework Core) on the server, and a Shared library for DTOs and common models.
File structure
Top-level solutions:
• BasicAuth/BasicAuth.sln
– Client (Blazor WASM)
– Server (ASP.NET Core API + Identity)
– Shared (DTOs)
• FlexibleAuth/FlexibleAuth.sln
– Client (Blazor WASM with custom authorize view)
– Server (API + Identity + custom authorization hooks)
– Shared (DTOs, custom Authorization attributes, policy providers)
Common patterns:
• Client/Pages and Shared/ components → UI layer
• Server/Controllers → API endpoints
• Server/Data → EF Core DbContext, migrations, seeders
• Shared/Authorization → extensibility points (attributes, handlers)
README
• Confirms focus on “Developing Flexible Authorization Capabilities with ASP.NET Core.”
• Implies comparison between a basic role-based approach and a flexible permission-based approach.
a. Main components
– Browser running Blazor WebAssembly (Client)
– ASP.NET Core API server (Server)
– SQL database for Identity and permissions (DbContext)
– Shared library (models, DTOs, auth policies)
– External OAuth/OIDC configuration endpoint (optional, via OidcConfigurationController)
b. Relationships & interactions
– User → Browser UI
– UI HTTP(S) calls → API endpoints (Authentication, User Admin, WeatherForecast)
– API ↔ Database (Identity tables, Permissions table for FlexibleAuth)
– Client retrieves OIDC metadata from server’s OidcConfigurationController
– Server’s Authorization handlers evaluate roles or permissions (BasicAuth vs. FlexibleAuth)
c. Architectural patterns
– Layered architecture (UI, API, Data, Shared)
– Separation of concerns (Client vs. Server vs. Shared)
– Extensible policy provider pattern in FlexibleAuth
d. Key technologies & frameworks
– Blazor WebAssembly, .razor pages, CustomAccountClaimsPrincipalFactory
– ASP.NET Core Identity, Entity Framework Core Migrations
– NSwag for API client generation
– Custom authorization attributes and handlers (FlexibleAuth)