Skip to content

Clarify VC without Holder Binding is returned directly in the VP Token - #783

Open
jogu wants to merge 2 commits into
mainfrom
clarify-vc-without-holder-binding
Open

Clarify VC without Holder Binding is returned directly in the VP Token#783
jogu wants to merge 2 commits into
mainfrom
clarify-vc-without-holder-binding

Conversation

@jogu

@jogu jogu commented Aug 27, 2026

Copy link
Copy Markdown
Collaborator

When require_cryptographic_holder_binding is false, implementers were unsure whether to return the bare W3C Verifiable Credential or a Verifiable Presentation envelope without a proof. Clarify that the Credential itself goes directly into the VP Token, and scope the nonce/aud and challenge/domain requirements in the jwt_vc_json and ldp_vc Presentation Response sections to the case where a Verifiable Presentation is returned.

Fixes #742

When require_cryptographic_holder_binding is false, implementers were
unsure whether to return the bare W3C Verifiable Credential or a
Verifiable Presentation envelope without a proof. Clarify that the
Credential itself goes directly into the VP Token, and scope the
nonce/aud and challenge/domain requirements in the jwt_vc_json and
ldp_vc Presentation Response sections to the case where a Verifiable
Presentation is returned.

Fixes #742
@brentzundel

Copy link
Copy Markdown
Collaborator

discuss in WG: @brentzundel will review

Comment thread 1.0/openid-4-verifiable-presentations-1_0.md Outdated
Comment thread 1.0/openid-4-verifiable-presentations-1_0.md Outdated
Comment thread 1.1/openid-4-verifiable-presentations-1_1.md Outdated
Co-authored-by: Christian Bormann <chris.bormann@gmx.de>
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.

Clarification on W3C Verifiable credentials related Structural expectations when require_cryptographic_holder_binding is false

7 participants