AuthZEN: The “OpenID Connect”
of Authorization
Gartner IAM Summit Grapevine 2025
Alex Olivier
Co-founder, Cerbos
David Brossard
CTO, Axiomatics
Homan
Farahmand
VP Analyst, Gartner
Omri Gazitt
Co-founder, Aserto
Agenda
Introduction
Why AuthZEN
What AuthZEN provides
Demo
Homan
Farahmand
Omri Gazitt
David
Brossard
Alex Olivier
State of IAM
• OAuth2, OIDC, SAML, JWT
• Workforce SSO: Okta, Entra, Ping Identity, …
• CIAM: Auth0, Cognito, AAD B2C, …
“n * m”
problem
Authentication is “solved” ✅
“n + m” problem
• No widespread standard or protocol (yet)
• Each app bakes-in domain-specific AuthZ
• Overprovisioned static roles, spaghetti code
• OWASP Top Ten #1 issue: Broken Access Control
Authorization is broken: ❌
“n + m” problem
OpenID AuthZEN Vision
• OAuth2, OIDC, SAML, JWT
• Workforce SSO: Okta, Entra, PingID, …
• CIAM: Auth0, Cognito, AAD B2C, …
Authentication is “solved”
• AuthZEN PEP-PDP API
• Each app externalizes authorization to PDP
• Commercial Workforce and CIAM solutions
Authorization is like authentication
“n + m” problem
OpenID
AuthZEN
Modern Authorization
Ecosystems, standards, & OSS
Policy as code (ABAC) Policy as data (ReBAC)
Casbin
TOPAZ
Open Policy Agent
NGAC
2016
2001
AuthZEN
2024
Zanzibar
2020
2014
ALFA
Business Drivers
Developer
Efficiency
Let developers focus on
business features and
delegate authorization to a
dedicated service
Audit &
Compliance
Produce access reviews that
make business sense &
access detailed audit trails
Efficient IAM
Avoid role explosions;
simplify JML
Secure by Design
Enable Zero Trust &
continuous enforcement
through runtime access
Identity Fabric
Enable interoperability
between apps and identity
components
Gartner Hype Cycle for Digital Identity, 2025
First
mention on
the Hype
Cycle
AuthZEN Charter https://openid.net/wg/authzen/
Policy
Enforcemen
t Externalized
authorization
service that
delivers fine-
grained access
decisions.
Define
management APIs
to distribute
policies from the
control plane to the
PDPs.
Retrieve metadata
from underlying
sources e.g.
directories,
databases…
Protect resources
(APIs, AI, Data,
processes).
Policy
Decision
Policy
Administratio
n
Policy
Information
OpenID AuthZEN Enables Defense-in-Depth
Identity Providers
IdP as Enforcement
(coarse-grained)
API Gateway as PEP
(medium-grained)
App code as PEP
(fine-grained)
Data Proxy as PEP
(fine-grained)
API Gateways App Frameworks DB Proxies
OpenID
Policy Decision Point
OpenID AuthZEN Architecture
COMPATIBILITY
NIST ABAC 800-162
OWASP API
AI MCP
NIST Zero Trust 800-207
Defense-in-Depth
What’s included in OpenID AuthZEN?
Batch Binary API Search API Discovery API
Binary AuthZ API
AuthZEN Drafts - A History
AuthZEN 1.0 Core:
• /evaluation endpoint: Draft 01 (Implementer’s
Draft – Nov 2024)
• /evaluations endpoint: Draft 02 (Jan 2025)
• /search endpoints: Draft 03 (Mar 2025)
• /.well-known (discovery) endpoint: Draft 04 (Oct
2025)
• Draft 05 WG vote for Final Specification (Oct 23,
2025)
• 60 day review and vote for Final Specification of
Draft 05 (in progress)
Scenario Event Draft Endpoints
App Code Identiverse 2024 0 /evaluation
App Code EIC 2024 1 /evaluation
App Code Authenticate 2024 2 + /evaluations
App Code Gartner IAM US 202
4
2 + /evaluations
API Gateway Gartner IAM Lon 202
5
2 + /evaluations
Search Identiverse 2025 3
/search, /.well-
known
IdP
Gartner IAM US
2025
4 /search
7 Interops
Binary API Sample Payload
https://openid.github.io/authzen/
Use Cases
● Transactional authorization
● API Access Control
● Address the OWASP API Top Ten
{
"subject": {
"type": "user",
"id": "Alice"
},
"action": {
"name": "view"
},
"resource": {
"type": "record",
"id": "1"
"properties": {
"ownerID": "Bob"
}
}
}
{
"decision": true
}
Reque
st
Respon
se
Batch Binary API: Sample Payload
Use Cases
● Same as previous API plus
● Functional access control
● UI access control
● Access to medium-sized datasets
● Access to fields of a given record…
{
"subject": {
"type": "user",
"id": "alice@example.com"
}, "resource": {
"type": "record",
"id": "123"
}, "evaluations": [{
"action": {
"name": "read"
}
},{
"action": {
"name": "edit"
}
}]}
{"evaluations": [
{"decision": true},
{"decision": false}
]}
Reque
st
Respon
se
Search API: Sample Payload
Search APIs
● Subject Search
○ Who can view record #1?
● Resource Search
○ Which record can Alice view?
● Action Search
○ What can Alice do on record #1?
Use Cases
● Dynamic data filtering
● Entitlement access review
● Entitlement provisioning
● Access matrix generation
● Authorization logic testing
{
"subject": {
"type": "user"
},
"action": {
"name": "view"
},
"resource": {
"type":
"record",
"id": "101"
}
}
{
"results": [
{
"type": "user",
"id": "bob"
},
{
"type": "user",
"id": "carol"
}]
}
Reque
st
Respon
se
Who can view
record 101?
Bob and Carol
Interop History
Initial Interops (June 2024 and later)
● The PDPs get together and prove interoperability with one another
● App-centric
API Gateway-centric Interop (March 2025)
● API gateways act as the PEP and show they can use any compatible PDP
IdP-centric Interop (December 2025)
● Identity providers (e.g. OAuth AS) can now interact with AuthZEN-based PDPs in a standard way (token
issuance, enrichment…)
Future Interops
● Externalized Authorization for SaaS & COTS
● Native support in app development frameworks
API Gateways as PEP
Policy Decision Points
(PDP)
Interoperable implementations (Dec. 2025)
TOPAZ
Identity Providers as
PEP
Gartner IAM December 2025 Interop
The Challenge
● OAuth is identity-centric
● Access based on scopes/claims is coarse-
grained
● Access still depends on app code
● No consistent access policy
● Lack of policy in OAuth makes audit &
compliance difficult
● OAuth focuses mostly on access
delegation rather than runtime access
control.
The solution
● Extend your IdP with an AuthZEN-
compatible PDP
● The IdP can then ask
○ “Should I issue this token?”
○ “Which claims should I inject into the
token?”
Extend OAuth with
AuthZEN to achieve
finer-grained near-
runtime access control
Gartner IAM December 2025 Interop Architecture
AuthZEN Call
Authenticate OAuth Code Flow
ID Token/AT/RT
AuthZEN Resource Search Request
AuthZEN Response
OIDC Auth
Server
AuthZEN-compatible
Policy Decision Point
TOPAZ
And now for something completely different
Live Demo!
2026 Roadmap
AuthZEN Partial
Evaluation
A generalization of the Search API
AuthZEN 1.0 API
Gateway Profile
Building on top of the API Gateway
March 2025 Interop
AuthZEN 1.0 IdP
Profile
Building on top of the IdP December
2025 Interop
AuthZEN 1.0 Events
(Shared Signals)
Integrating with our sibling WG
Call to Action
• Attend one or more of the AuthZEN
interop showcase sessions
• Create an AuthZEN-based
Authorization Control Plane for your
enterprise (just like you did for
OpenID-based SSO)
• Externalize the authorization for your
internal apps whenever possible
• Encourage your SaaS vendors to
become AuthZEN-compliant and plug
into your Authorization Control Plane
Session Information
Tuesday (today)
● 12 to 12:30pm
● 2 to 2:30pm
● 3:45 to 4:15pm
Wednesday (tomorrow)
● 10:30 to 11am
● 12 to 12:30pm
Room: Austin 1
Where to find us
• AuthZEN mailing list: https://openid.net/wg/authzen
• GitHub: https://github.com/openid/authzen
• OpenID Slack: #wg-authzen
• Meeting notes & docs: https://hackmd.io/@oidf-wg-authzen
• Email: omri@aserto.com, david.brossard@axiomatics.com

OpenID AuthZEN Overview - Gartner IAM 25

  • 1.
    AuthZEN: The “OpenIDConnect” of Authorization Gartner IAM Summit Grapevine 2025 Alex Olivier Co-founder, Cerbos David Brossard CTO, Axiomatics Homan Farahmand VP Analyst, Gartner Omri Gazitt Co-founder, Aserto
  • 2.
    Agenda Introduction Why AuthZEN What AuthZENprovides Demo Homan Farahmand Omri Gazitt David Brossard Alex Olivier
  • 3.
    State of IAM •OAuth2, OIDC, SAML, JWT • Workforce SSO: Okta, Entra, Ping Identity, … • CIAM: Auth0, Cognito, AAD B2C, … “n * m” problem Authentication is “solved” ✅ “n + m” problem • No widespread standard or protocol (yet) • Each app bakes-in domain-specific AuthZ • Overprovisioned static roles, spaghetti code • OWASP Top Ten #1 issue: Broken Access Control Authorization is broken: ❌
  • 4.
    “n + m”problem OpenID AuthZEN Vision • OAuth2, OIDC, SAML, JWT • Workforce SSO: Okta, Entra, PingID, … • CIAM: Auth0, Cognito, AAD B2C, … Authentication is “solved” • AuthZEN PEP-PDP API • Each app externalizes authorization to PDP • Commercial Workforce and CIAM solutions Authorization is like authentication “n + m” problem OpenID AuthZEN
  • 5.
    Modern Authorization Ecosystems, standards,& OSS Policy as code (ABAC) Policy as data (ReBAC) Casbin TOPAZ Open Policy Agent NGAC 2016 2001 AuthZEN 2024 Zanzibar 2020 2014 ALFA
  • 6.
    Business Drivers Developer Efficiency Let developersfocus on business features and delegate authorization to a dedicated service Audit & Compliance Produce access reviews that make business sense & access detailed audit trails Efficient IAM Avoid role explosions; simplify JML Secure by Design Enable Zero Trust & continuous enforcement through runtime access Identity Fabric Enable interoperability between apps and identity components
  • 7.
    Gartner Hype Cyclefor Digital Identity, 2025 First mention on the Hype Cycle
  • 8.
    AuthZEN Charter https://openid.net/wg/authzen/ Policy Enforcemen tExternalized authorization service that delivers fine- grained access decisions. Define management APIs to distribute policies from the control plane to the PDPs. Retrieve metadata from underlying sources e.g. directories, databases… Protect resources (APIs, AI, Data, processes). Policy Decision Policy Administratio n Policy Information
  • 9.
    OpenID AuthZEN EnablesDefense-in-Depth Identity Providers IdP as Enforcement (coarse-grained) API Gateway as PEP (medium-grained) App code as PEP (fine-grained) Data Proxy as PEP (fine-grained) API Gateways App Frameworks DB Proxies OpenID Policy Decision Point
  • 10.
    OpenID AuthZEN Architecture COMPATIBILITY NISTABAC 800-162 OWASP API AI MCP NIST Zero Trust 800-207 Defense-in-Depth
  • 11.
    What’s included inOpenID AuthZEN? Batch Binary API Search API Discovery API Binary AuthZ API
  • 12.
    AuthZEN Drafts -A History AuthZEN 1.0 Core: • /evaluation endpoint: Draft 01 (Implementer’s Draft – Nov 2024) • /evaluations endpoint: Draft 02 (Jan 2025) • /search endpoints: Draft 03 (Mar 2025) • /.well-known (discovery) endpoint: Draft 04 (Oct 2025) • Draft 05 WG vote for Final Specification (Oct 23, 2025) • 60 day review and vote for Final Specification of Draft 05 (in progress) Scenario Event Draft Endpoints App Code Identiverse 2024 0 /evaluation App Code EIC 2024 1 /evaluation App Code Authenticate 2024 2 + /evaluations App Code Gartner IAM US 202 4 2 + /evaluations API Gateway Gartner IAM Lon 202 5 2 + /evaluations Search Identiverse 2025 3 /search, /.well- known IdP Gartner IAM US 2025 4 /search 7 Interops
  • 13.
    Binary API SamplePayload https://openid.github.io/authzen/ Use Cases ● Transactional authorization ● API Access Control ● Address the OWASP API Top Ten { "subject": { "type": "user", "id": "Alice" }, "action": { "name": "view" }, "resource": { "type": "record", "id": "1" "properties": { "ownerID": "Bob" } } } { "decision": true } Reque st Respon se
  • 14.
    Batch Binary API:Sample Payload Use Cases ● Same as previous API plus ● Functional access control ● UI access control ● Access to medium-sized datasets ● Access to fields of a given record… { "subject": { "type": "user", "id": "alice@example.com" }, "resource": { "type": "record", "id": "123" }, "evaluations": [{ "action": { "name": "read" } },{ "action": { "name": "edit" } }]} {"evaluations": [ {"decision": true}, {"decision": false} ]} Reque st Respon se
  • 15.
    Search API: SamplePayload Search APIs ● Subject Search ○ Who can view record #1? ● Resource Search ○ Which record can Alice view? ● Action Search ○ What can Alice do on record #1? Use Cases ● Dynamic data filtering ● Entitlement access review ● Entitlement provisioning ● Access matrix generation ● Authorization logic testing { "subject": { "type": "user" }, "action": { "name": "view" }, "resource": { "type": "record", "id": "101" } } { "results": [ { "type": "user", "id": "bob" }, { "type": "user", "id": "carol" }] } Reque st Respon se Who can view record 101? Bob and Carol
  • 16.
    Interop History Initial Interops(June 2024 and later) ● The PDPs get together and prove interoperability with one another ● App-centric API Gateway-centric Interop (March 2025) ● API gateways act as the PEP and show they can use any compatible PDP IdP-centric Interop (December 2025) ● Identity providers (e.g. OAuth AS) can now interact with AuthZEN-based PDPs in a standard way (token issuance, enrichment…) Future Interops ● Externalized Authorization for SaaS & COTS ● Native support in app development frameworks
  • 17.
    API Gateways asPEP Policy Decision Points (PDP) Interoperable implementations (Dec. 2025) TOPAZ Identity Providers as PEP
  • 18.
    Gartner IAM December2025 Interop The Challenge ● OAuth is identity-centric ● Access based on scopes/claims is coarse- grained ● Access still depends on app code ● No consistent access policy ● Lack of policy in OAuth makes audit & compliance difficult ● OAuth focuses mostly on access delegation rather than runtime access control. The solution ● Extend your IdP with an AuthZEN- compatible PDP ● The IdP can then ask ○ “Should I issue this token?” ○ “Which claims should I inject into the token?” Extend OAuth with AuthZEN to achieve finer-grained near- runtime access control
  • 19.
    Gartner IAM December2025 Interop Architecture AuthZEN Call Authenticate OAuth Code Flow ID Token/AT/RT AuthZEN Resource Search Request AuthZEN Response OIDC Auth Server AuthZEN-compatible Policy Decision Point TOPAZ
  • 20.
    And now forsomething completely different Live Demo!
  • 21.
    2026 Roadmap AuthZEN Partial Evaluation Ageneralization of the Search API AuthZEN 1.0 API Gateway Profile Building on top of the API Gateway March 2025 Interop AuthZEN 1.0 IdP Profile Building on top of the IdP December 2025 Interop AuthZEN 1.0 Events (Shared Signals) Integrating with our sibling WG
  • 22.
    Call to Action •Attend one or more of the AuthZEN interop showcase sessions • Create an AuthZEN-based Authorization Control Plane for your enterprise (just like you did for OpenID-based SSO) • Externalize the authorization for your internal apps whenever possible • Encourage your SaaS vendors to become AuthZEN-compliant and plug into your Authorization Control Plane Session Information Tuesday (today) ● 12 to 12:30pm ● 2 to 2:30pm ● 3:45 to 4:15pm Wednesday (tomorrow) ● 10:30 to 11am ● 12 to 12:30pm Room: Austin 1
  • 23.
    Where to findus • AuthZEN mailing list: https://openid.net/wg/authzen • GitHub: https://github.com/openid/authzen • OpenID Slack: #wg-authzen • Meeting notes & docs: https://hackmd.io/@oidf-wg-authzen • Email: omri@aserto.com, david.brossard@axiomatics.com

Editor's Notes

  • #2 Quick intro: Why we are here (Homan) Q1: What is AuthZen? (Omri) Q2: How does it work? (David) Q3: What is an example of a vendor adopting AuthZen? (Alex)
  • #3 Homan presents a slide contrasting the state of AuthN and AuthZ
  • #4 Homan introduces the AuthZEN vision
  • #5 Historical slide that introduces current ecosystems and previous standards efforts, with AuthZEN aiming to unify all the ecosystems. Homan could either present or delegate to Omri.
  • #6 More efficient IAM → avoid role explosion Audit & Compliance → access reviews that make sense & audit trails Developer efficiency → let devs focus on business features and delegate AuthN/AuthZ to purpose-built services Identity Fabric → Interoperability between identity components Secure by design → enable Zero Trust & continuous enforcement through runtime access
  • #7 Adopting AuthZEN: Reduces effort and complexity by simplifying fine-grained authorization with a standard interface, eliminating custom-made integrations. Accelerates adoption by promoting externalized authorization in applications. Centralizes authorization policy management for improved auditability and compliance. Ensures consistent access control and dynamic authorization decisions. Decreases reliance on proprietary systems, thereby reducing the risk of vendor lock-in.
  • #10 NIST ABAC 800-162 Architecture NIST Zero Trust 800-207 Architecture OWASP API Architecture AI MCP Architecture All rely on the proxy approach. This is what AuthZEN enables.
  • #11 Binary AuthZ API AuthZEN provides a standard schema for the request and the response with the ability to enrich decisions. Can Alice view record #123? ✅. Batch Binary API AuthZEN provides a mechanism to send batch requests in one go reusing common elements for all requests. Can Alice view/edit record #123? ✅❌. Search API Rather than receive a decision, get the list of entitled items back from the API. AuthZEN enables user, resource, and action search. Discovery API Each PDP can expose the AuthZEN capabilities it supports and where to find them. This is inline with other identity discovery endpoints.
  • #13 Omri talks about the simplicity of the AuthZEN PDP API design.
  • #17 David talks about current state of interoperable implementations.
  • #21 David goes over the CTA.
  • #22 David goes over the CTA.
  • #23 David brings us home.