Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarification on the aud claim in JWT Request Object #316

Closed
fmarino-ipzs opened this issue Jun 17, 2024 · 2 comments · Fixed by #380
Closed

Clarification on the aud claim in JWT Request Object #316

fmarino-ipzs opened this issue Jun 17, 2024 · 2 comments · Fixed by #380
Assignees
Labels
Milestone

Comments

@fmarino-ipzs
Copy link
Collaborator

In the current version of this spec, the aud parameter is defined as the identifier of the PID/(Q)EAA Provider. It’s recommended to use the URL of the specific endpoint that consumes the JWT.

@peppelinux
Copy link
Member

using the url of the endpoint makes it not fully compliant with openid4vci where the issuer unique identifier is enough.

see the thread below and join in there if possibile for you
openid/OpenID4VCI#265

@peppelinux
Copy link
Member

In the meeting of 31 July 2024 we have decided to

  • align the current issuance documentation with the mandatory usage of the aud value set with the endpoint url

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

Successfully merging a pull request may close this issue.

2 participants