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

Value used for 'aud' in SD-JWT key-binding JWT needs to be normatively defined #350

Closed
jogu opened this issue Nov 28, 2024 · 1 comment · Fixed by #357
Closed

Value used for 'aud' in SD-JWT key-binding JWT needs to be normatively defined #350

jogu opened this issue Nov 28, 2024 · 1 comment · Fixed by #357
Labels
Milestone

Comments

@jogu
Copy link
Collaborator

jogu commented Nov 28, 2024

There doesn't appear to be anywhere that the actual value to be used in 'aud' in an SD-JWT key binding JWT is defined.

SD-JWT only says:

aud: REQUIRED. The intended receiver of the Key Binding JWT. How the value is represented is up to the protocol used and out of scope of this specification.

SD-JWT VC doesn't seem to say anything normative.

OID4VP doesn't seem to say anything normative.

HAIP doesn't currently say anything normative, but I'm also not sure HAIP is the right place to define this.

I suggest adding a clause in the SD-JWT credential format section in VP saying:

aud in the Key Binding JWT MUST be the client_id.

@awoie
Copy link
Contributor

awoie commented Nov 28, 2024

There doesn't appear to be anywhere that the actual value to be used in 'aud' in an SD-JWT key binding JWT is defined.

SD-JWT only says:

aud: REQUIRED. The intended receiver of the Key Binding JWT. How the value is represented is up to the protocol used and out of scope of this specification.

SD-JWT VC doesn't seem to say anything normative.

OID4VP doesn't seem to say anything normative.

HAIP doesn't currently say anything normative, but I'm also not sure HAIP is the right place to define this.

I suggest adding a clause in the SD-JWT credential format section in VP saying:

aud in the Key Binding JWT MUST be the client_id.

I agree that this is needed.

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

Successfully merging a pull request may close this issue.

3 participants