jwt

JWT authentication in ASP.NET Core involves configuring Bearer token validation in Program.cs using shared JwtSettings, protecting endpoints with .RequireAuthorization(), and defining authorization policies. The Skill integrates with ASP.NET Core's standard authentication pipeline to validate tokens across services and enforce access control rules.

JWT token types serve different authentication scenarios: user tokens identify end users, service tokens authenticate service-to-service communication, and delegated tokens enable one service to act on behalf of another. The Skill supports all three types using consistent JwtSettings configuration across Sorcha services.

Issue tokens by generating a Bearer token with the appropriate claims for your tenant context. Validate tokens by configuring ASP.NET Core authentication middleware with shared issuer settings from Sorcha.ServiceDefaults. The Skill handles token validation and applies tenant isolation within authorization policies.

401 errors indicate missing or invalid JWT tokens; 403 errors mean the token is valid but lacks required authorization claims. Verify token validity, check that endpoints have .RequireAuthorization() applied, and confirm authorization policies match the token's claims and tenant context.

Yes, Sorcha.ServiceDefaults provides the shared JwtSettings configuration required for consistent token issuing and validation across services. The Skill relies on this dependency to maintain a single source of truth for JWT authentication parameters in your microservice architecture.

JWT tokens are stateless by design and cannot be revoked until expiration. The Skill supports token revocation strategies through authorization policies that check against external blocklists or invalidation sources, enabling you to deny access to tokens before their expiration time.