Implementing authorization in web applications and APIs
summary
Argues that puting permissions into signed tokens fails for changing permissions and ambiguous meanings, and builds a prototype authorization provider as an ASP.NET Core Web API plus a client library that returns mapped roles and permissions, supports claims transformation, a dynamic policy provider, custom requirement handlers and resource‑based checks; notes need for caching on the client and that the approach works well for API/feature gating but breaks down once authorization becomes deep business logic tied to object properties.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:30Authorization is hard!
- 5:08Modern Applications
- 7:42Overloaded Security Token
- 10:09Token Usage
- 22:57Client Integration Strategies
- 30:59ASP.NET Core Authorization
- 39:31Custom Requirements
- 47:02Example: Patient Resource
- 50:32Conclusion
related talks
01h 02mImplementing authorization in web applications and APIs
58mImplementing Authorization in Web Applications and APIs
58mImplementing authorization in web applications and APIs
54mAuthorization for modern Applications
36mFlexible Authorisation with ASP.NET Core 7.0
01h 07mGetting Authorization Right in .NET: Patterns, Pitfalls...
51mDeveloping Flexible Authorisation Capabilities in ASP NET Core
47mDeveloping Flexible Authorisation Capabilities in ASP.NET Core
