Meeting Notes 2026‐09‐03 - openid/authzen GitHub Wiki
Attendees
Roland
Omri
Jeff L
Nate
Dave Hyland
George
Dave B
Vatsal Gupta
Victor Lu
Agenda
(Jeff) Do we decide leads for the new drafts at the next meeting?
(Omri) Do we need a v1.1 spec to add a top-level options object to the information model + a top-level context to the evalutions request?
Gartner IAM participation
Notes
Open item: general extensibility mechanism that obligations will layer over. Karl put together a couple gists to address this. Both Jeff and Omri are happy to contribute.
Obligations are not finalized and have an opportunity to piggy-back on Karl's proposal.
The original draft makes sure it's backwards/forward compatible.
Could we invent a negotiation mechanism to determine which mandatory extensions the PDP supports so the PEP can act accordingly? This could occur through either the request context object and the metadata endpoint of the PDP.
Omri: the 4 drafts we voted into the core spec last week were now merged into the main branch of the AuthZEN spec repo.
We agreed in the previous meeting that we would NOT introduce a v1.1 spec.
Volunteers for the new drafts:
Token exchange & scopes (OAuth to AuthZEN model mapping exercise): Omri, Roland, David B., Alex O. See prior art at the IdP interop.
COAZ would be a good candidate: let's target an interop for Gartner IAM March '27
Token exchange spec scenario: have the IdP consult the PDP in an ID-JAG scenario. The AI IAM scenario is building towards ID-JAG. It would be interesting to build an interop scenario illustrating how an IdP would call out to an AuthZEN PDP.
David will discuss with other chairs & Gail re. possible panel proposal for Gartner.
Let's also consider other outlets e.g. MCP Summit. See the MCP Github for SEP (fine-grained authz).
Open issues
ARAP/AROP: let's rope in one of the co-chairs. David to follow up with other chairs.