The Future of Authorization in Applications
summary
Identifies four problems—chaos, complexity, velocity and confidence—and claims authorization needs structure not slogans, citing Google Zanzibar, Policy as Code and concrete engines: Open Policy Agent (Rego), AWS Cedar and OpenFGA. Describes a built end‑to‑end admin layer called OPAL (Docker compose, git branch → policy sync, OPA + Cedar supported, OpenFGA planned). Argues most decisions fit a check function (covers ~99–99.5%), supports partial‑evaluation SQL results, and solves graph scale by sharding plus eventual consistency for multi‑region deployments.
AI-written summary · about
chapters (10)
- 0:00Future authorization trends
- 2:50Modern auth problems
- 13:30Structured authorization
- 17:46Auth design patterns
- 21:40Authorization frameworks
- 29:25RBAC ABAC ReBAC models
- 32:57Declarative auth languages
- 38:35Open source auth tools
- 41:25Dev experience challenges
- 43:34Performance and scalability in relationship-based access control
related talks
29mAuthz as a dev workflow
49mLove, Hate, And Policy Languages
43mApplication Code of Conduct - Full-Stack Policy as Code
32mAuthz as a Dev Workflow: Architecting Better Cloud Native Apps
24mExpanding beyond authentication with emerging authorization standards
27mSecurity-by-construction: How to weave authorization into modern app stacks using Open Policy Agent
54mAuthorization for modern Applications
32mImplementing Authorization