Require x5c in OID4VCI Appendix D key attestations #338
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(Not discussed in WG yet, but given the timeline for HAIP 1.0 I opened a PR so there is some concrete text to discuss.)
In the same way as is already done for wallet attestations, signed requests and issuer metadata, require x509 to be used as the mechanism for establishing trust in key attestations.
The language used is mostly lifted from existing language in other places we mandate the
x5cheader.closes #336