Skip to content

Conversation

@TimoGlastra
Copy link
Contributor

Made a start at rich authorization requests for OpenID4VCI:

  • models for token request, token response, authorization request, authorization challenge request
  • additional validations for RAR
  • parsing RAR for OID4VCI server side
  • using RAR for OID4VCI on holder side

I think similar to what we have done with scope, requiring the user of this library to actually provide the scope, we should require the user to pass the authorization_details. However like we did with scope, we can create utils. Currently we have an util to extract for a set of credential configuration ids. We should create a combined method:

  • if scope -> use the scope
  • if no scope and issuer supports RAR type openid_credential -> use RAR
  • else throw error

This sill allows full control, while also accomodating the standard flow

Signed-off-by: Timo Glastra <[email protected]>
…one breaking change requiring a transaction_id in the deferred credential response. For this reason we replaced the Draft16 support with V1. All other drafts are still supported.

Signed-off-by: Timo Glastra <[email protected]>
Signed-off-by: Timo Glastra <[email protected]>
@changeset-bot
Copy link

changeset-bot bot commented Oct 18, 2025

⚠️ No Changeset found

Latest commit: 4be5390

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Base automatically changed from feat/update-draft-16-to-v1 to main October 21, 2025 08:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants