Attendees

• Julio Auto
• Alex Babeanu
• Jeff Lombardo (AWS)
• Omri
• Karl Mcguinness
• Vladi Berger
• John Jiang
• Michiel Trimpe
• Roland Baum
• David Brossard
• Nate Yocom

Agenda

• Voting to bring in the following drafts into the WG:
  • AuthZEN Access Request OAuth Profile (AROP)
  • AuthZEN Profile for OAuth 2.0 Token Issuance
  • AuthZEN Binding for OAuth 2.0 Token Exchange
  • AuthZEN Profile for Authorization Claims in JWT Access Tokens
• AOB

Notes

Voting Results

AuthZEN Access Request OAuth Profile (AROP)

• Approves: 9
• Objects: 0
• Abstains: 1

Outcome: Approved

AuthZEN Profile for OAuth 2.0 Token Issuance

• Approves: 8
• Objects: 0
• Abstains: 2

Outcome: Approved

Notes:

• (Karl) Where to cut this? do we need to separate issuance from exchange?
• (Jeff) +1 to this

AuthZEN Binding for OAuth 2.0 Token Exchange

• Approves: 10
• Objects: 0
• Abstains: 1

Outcome: Approved

Notes:

• Same comments apply as for issuance

AuthZEN Profile for Authorization Claims in JWT Access Tokens

• Approves: 7
• Objects: 0
• Abstains: 4

Outcome: Approved

Notes:

• (Jeff) on the model of Karl, this feels more like AuthZEN for SCIM. It is more generic and requires less prerequisites
• (Michiel) not in favor putting multiple Search calls in the call-path of an AS. The SCIM perspective I can agree with though. Thus abstaining though.

Other Discussion

• (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?