How mgernand/aspnetcore.authorization.permissions works
Project type and purpose
• This is an open-source .NET 6+ library (AspNetCore.Authorization.Permissions) plus a set of sample ASP.NET Core Razor-Pages applications.
• Purpose: provide a dynamic, permission-based authorization framework for ASP.NET Core, with extensible storage (EF Core, MongoDB) and optional multi-tenant support.
File structure
• Top-level “src” folder holds library projects:
• Abstractions (interfaces, extensions)
• Core authorization implementation
• ASP.NET Core Identity integration (core, EF Core store, MongoDB store)
• Shared extensions and stores
• “samples” folder has four Razor-Pages web apps showing EF Core (“SamplePermissions”, “SampleTenant”) and MongoDB (“MongoSamplePermissions”, “MongoSampleTenant”) usage.
• “tests” contains unit tests for core and integration tests for EF Core and MongoDB implementations.
Key README insights
• Library is split into two major parts:
a. Base definitions, extension methods, policy handlers (ClaimsPrincipal extensions, RequirePermissionAttribute).
b. Storage/provider implementations for ASP.NET Core Identity (EF Core and MongoDB).
• Optional multi-tenant: tenants contribute extra role permissions and tenant claims.
Main components & their interactions
a. Web Host / Sample Application
• Razor Pages controllers and Minimal API endpoints.
• References: AspNetCore.Authorization.Permissions library + Identity + EF Core or MongoDB packages.
b. ASP.NET Core Pipeline
1. HTTP Request → Authentication middleware (ASP.NET Identity cookies or JWT)
2. PermissionsAuthorization middleware (AddPermissionsAuthorization)
3. Policy evaluation via AuthorizationPolicyProvider
4. RequirePermissionAttribute / Minimal API RequirePermission handlers
c. Permissions Core
• IClaimsProvider & IUserPermissionsService interfaces (in Abstractions).
• PermissionEndpointConventionBuilderExtensions, PermissionPolicyHandler, PermissionRequirement.
• ClaimsPrincipalExtensions → HasPermission()
d. Identity Integration
• Extensions.Identity.Permissions.Core: generic managers, stores interfaces, DI setup.
• AspNetCore.Identity.Permissions.EntityFrameworkCore: EF Core model configurations, DbContextExtensions.
• AspNetCore.Identity.Permissions.MongoDB: Schema ensure scripts, MongoDB stores.
e. Data Stores
• InvoicesContext (EF Core) backed by SQLite/SQL Server.
• MongoDB database for tenants and permissions.
f. Multi-tenant components
• ITenantProvider adds tenant claim
• TenantStore & TenantManager load tenant roles and permissions
Architectural patterns & design principles
• Layered architecture: Abstractions → Core services → Implementations
• Plugin/Provider pattern: IClaimsProvider, ITenantProvider, IPermissionStore allow swapping persistence.
• Policy/Strategy pattern for authorization policies
• Dependency Injection for all extension points
Don’t overthink—separate into as many components as makes sense
• How DI brings together Abstractions + Core + chosen Implementation (EF or Mongo)