Skip to content

The SD-JWT DC does not CONTAIN the Key Binding JWT #289

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

Open
Denisthemalice opened this issue Dec 7, 2024 · 1 comment
Open

The SD-JWT DC does not CONTAIN the Key Binding JWT #289

Denisthemalice opened this issue Dec 7, 2024 · 1 comment

Comments

@Denisthemalice
Copy link

Section 3.2 states:

SD-JWT VCs MUST be encoded using the SD-JWT format defined in Section 5 of [I-D.ietf-oauth-selective-disclosure-jwt]. A presentation of an SD-JWT VC MAY contain a Key Binding JWT.

Note that in some cases, an SD-JWT VC MAY have no selectively disclosable claims, and therefore the encoded SD-JWT will not contain any Disclosures.

The SD-JWT DC does not CONTAIN the Key Binding JWT. See the revised Figure 1. See #285.
However, a SD-JWT VC CAN be ASSOCIATED with a Key Binding JWT

The following changes are proposed:

A presentation of an SD-JWT DC CAN be associated with a Key Binding JWT.

Note that in some cases, an SD-JWT DC MAY have no selectively disclosable claims, and therefore the encoded SD-JWT will not be associated with any Disclosures.

@babisRoutis
Copy link
Contributor

Although, I agree with the proposed idea (I also think that SD-JWT doesn't contain a KB-JWT, rather a KB-JWT may be associated to an SD-JWT presentation), yet I feel that this proposal should target SD-JWT and not SD-JWT-VC.

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

No branches or pull requests

2 participants