AuthEN: Standards for modern authorization
summary
OZen defines a simple PEP→PDP JSON: a request with subject action resource plus optional context and a response that is true or false, and it already has multiple interoperable PDP implementations after about a year of work. The group demonstrates a live interop “to‑do” app that queries different PDPs and a plan for box-carring (batching multiple evals) in v1.1, plus event delivery via shared signals/CAPE and policy discovery/management for audits and continuous revocation.
AI-written summary · about
chapters (13)
- 0:00Introduction and setup
- 1:31Panel introductions
- 6:08Authentication vs authorization
- 8:16Modern authorization challenges
- 10:24Fine-grained access control
- 14:59Policy-based authorization
- 19:58Real-time authorization
- 25:43Authorization ecosystems
- 28:52Origin of Oden standard
- 33:47Oden implementation draft
- 39:28Call to action for Oden
- 41:10Next steps in Oden API
- 44:18Q&A session
related talks
30mAuthZEN in Practice: Standardizing Authorization for Cloud Native Platforms and Agents
41mBuilding Modern Authorization: A Practical Guide To Centralized, Distributed, and...
51mAuthorization beyond @RolesAllowed
29mAuthz as a dev workflow
46mBearer of Good News
46mA Deep Dive into the Past, Present & Future of OAuth
45mThe Future of Authorization in Applications
15mFrom OpenID Connect to OpenID AuthZEN