Authorization for modern Applications
summary
Argues a concrete architecture: keep identity (OpenID Connect/OAuth2 tokens and claims) separate from authorization and run permissions from a runtime policy store called PolicyServer (open source on GitHub with a commercial UI). Shows a client library, middleware and ASP.NET Core policy-based authorization handlers that evaluate hospital-style permissions (doctor vs nurse, per-API scopes) and discusses caching, freshness and why tokens are for identity not mutable permission lists — it works in multiple real deployments.
AI-written summary · about
chapters (7)
- 0:00The need for authorization
- 3:51Common authorization patterns
- 14:12Identity vs. authorization
- 27:36Building a policy engine
- 31:52Integration strategies
- 43:00Advanced policy handling
- 47:33Managing complex hierarchies
related talks
49mAuthorization for Modern Applications
58mImplementing Authorization in Web Applications and APIs
01h 02mImplementing authorization in web applications and APIs
56mImplementing authorization in web applications and APIs
58mImplementing authorization in web applications and APIs
01h 07mGetting Authorization Right in .NET: Patterns, Pitfalls...
45mThe Future of Authorization in Applications
51mAuthentication and Authorization in ASP.NET Core 2
