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

Relying Party Solution - SD-JWT Presentation - KB-JWT #423

Closed
pietroACN opened this issue Sep 25, 2024 · 1 comment · Fixed by #427
Closed

Relying Party Solution - SD-JWT Presentation - KB-JWT #423

pietroACN opened this issue Sep 25, 2024 · 1 comment · Fixed by #427
Assignees
Milestone

Comments

@pietroACN
Copy link

pietroACN commented Sep 25, 2024

The usage of a Key Binding JWT (KB-JWT) is a key element as it needs to be tied to a specific SD-JWT when its payload includes a hash of the SD-JWT in its sd_hash claim.

At the same time it needs prove possession of of the private key of the associated key pair.
To enforce this a Key Binding JWT (KB-JWT) signature must be verified by the same public key included (or referenced) in the SD-JWT.

The actual 0.8.0 documentation misses to provide such signature requirement, thus there's need to explicitly describe and require such key-binding detail.

@peppelinux
Copy link
Member

Related PR #427

@peppelinux peppelinux self-assigned this Sep 30, 2024
@peppelinux peppelinux added this to the 0.8.1 milestone Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging a pull request may close this issue.

2 participants