Skip to content

Building Interactive Authorization on top of first party apps draft#736

Open
mickrau wants to merge 11 commits into
mainfrom
719-revisiting-building-iae-on-top-of-first-party-apps-draft
Open

Building Interactive Authorization on top of first party apps draft#736
mickrau wants to merge 11 commits into
mainfrom
719-revisiting-building-iae-on-top-of-first-party-apps-draft

Conversation

@mickrau

@mickrau mickrau commented May 4, 2026

Copy link
Copy Markdown
Contributor

rough draft for further discussion.

Changes (among others):

  • change Interactive Authorization Endpoint to Interactive Authorization using Authorization Challenge Endpoint
  • remove status = (require_interactionok) and use (HTTP 401 with error: insufficient_authorization) and (HTTP 200 + authorization_code) instead

I kept the order of the sections so that you can see at a glance what has changed.

@mickrau mickrau requested review from GarethCOliver and fkj May 4, 2026 12:44
@mickrau mickrau linked an issue May 4, 2026 that may be closed by this pull request

@fkj fkj left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally I think this is really nice! It does not feel like a hack, but quite natural. I also think it reads pretty well. I've added a lot of nits and some points for discussion.
@mickrau It would be great if you could take a look and merge the ones you agree with/discard the ones you don't. Sorry it took me so long to review this!

Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md Outdated
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md Outdated
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md Outdated
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md Outdated
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md Outdated
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md Outdated
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md Outdated
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md Outdated
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md Outdated
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md Outdated
mickrau and others added 2 commits May 18, 2026 16:53
Co-authored-by: Frederik Krogsdal Jacobsen <fkj@users.noreply.github.com>
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md Outdated
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md Outdated
@mickrau mickrau marked this pull request as ready for review May 22, 2026 13:38
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md Outdated
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md Outdated
Comment thread 1.1/discussion/comparison_iae_1stpartyapp.md Outdated
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md Outdated
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md Outdated
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md Outdated
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md Outdated
Comment thread 1.1/openid-4-verifiable-credential-issuance-1_1.md
Co-authored-by: Judith <59833642+ju-cu@users.noreply.github.com>
Co-authored-by: Paul Bastian <paul.bastian@posteo.de>
Co-authored-by: Micha Kraus <7931215+mickrau@users.noreply.github.com>
@mickrau

mickrau commented Jun 11, 2026

Copy link
Copy Markdown
Contributor Author

Thank you for the feedback. I have resolved most of the suggestions. Aside from a few editorial todos, there are two open questions left to address:

  • Naming Convention: Should we rename urn:openid:dcp:ia:redirect_to_web to urn:openid:dcp:ia:method_via_web?
  • Error Handling: Should we stay with HTTP 401 (as used in FiPA example) or switch to HTTP 400 (as used in FiPA normative text)?

@fkj

fkj commented Jun 12, 2026

Copy link
Copy Markdown
Member
  • Naming Convention: Should we rename urn:openid:dcp:ia:redirect_to_web to urn:openid:dcp:ia:method_via_web?

I think yes, since people might forget about the URN prefix and think it's the same thing. A completely different name avoids confusion.

  • Error Handling: Should we stay with HTTP 401 (as used in FiPA example) or switch to HTTP 400 (as used in FiPA normative text)?

I think 401 makes more sense when considering the HTTP semantics.

Comment thread 1.1/discussion/comparison_iae_1stpartyapp.md Outdated
Co-authored-by: Micha Kraus <7931215+mickrau@users.noreply.github.com>
@openid openid deleted a comment from mkrabdr Jun 17, 2026
@fkj fkj self-requested a review June 17, 2026 10:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

revisiting building IAE on top of first party apps draft

6 participants