match inherited vcts with credential_type for SD-JWT VC
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
The SD-JWT VC annex (from #22) currently says a CredentialQuery matches SD-JWT VCs whose vct is identical to credential_type (case-sensitive text comparison). OpenID4VP's vct_values is looser: "The Wallet MAY return Credentials that inherit from any of the specified types, following the inheritance logic defined in SD-JWT VC".
We need to decide whether DCHP:
- requires exact
vctequality (simple, predictable, no type-metadata resolution needed on the wallet); - allow matching against
aka_vctstoo ( https://www.ietf.org/archive/id/draft-ietf-oauth-sd-jwt-vc-19.html#name-other-credential-types-aka_ ) - allows or requires matching on inherited types, in which case the wallet needs the type metadata chain at matching time;
- leaves this to the credential format definition / ecosystem.
Related to #46 (making credential_type an array), since both concern what credential_type matches. The annex added for #22 carries an editor's note pointing at this question.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the SD-JWT VC annex added for #22 and its editor’s note, then compare the current exact vct rule with OpenID4VP’s vct_values inheritance wording and the aka_vcts definition in the linked SD-JWT VC draft. Review #46 because it also concerns what credential_type matches; done means reaching and documenting a decision among exact matching, aka_vcts, inherited types, or format-specific behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100