Skip to content

Conversation

@awoie
Copy link
Collaborator

@awoie awoie commented Jul 25, 2025

Logic behind this and based on the following that is already in the OID4VCI spec:

  • if a credential configuration contains cryptographic_binding_methods_supported, proof(s) have to be provided
  • if nonce_endpoint present, then wallet must provide c_nonce in proof(s)
  • if nonce_endpoint present, then the issuer must check that the nonce in the proof(s) matches the provided c_nonce

Hence, all we need to do is to require nonce_endpoint to be present if there is a credential configuration that requires key binding.

Editorially, I'm not sure if the newline is required @jogu

closes #149

Co-authored-by: Joseph Heenan <joseph@authlete.com>
@jogu
Copy link
Contributor

jogu commented Aug 14, 2025

Agreement on today's WG call: one more review then we'll merge

@Sakurann Sakurann merged commit 14e0f25 into main Aug 19, 2025
2 checks passed
@Sakurann Sakurann added this to the 1.0 Final milestone Oct 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

clarify if c_nonce is optional or mandatory?

5 participants