Authorization Details claims
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
The Appendix introduces specific claims for Authorization Details for mdoc and sd-jwt vc type credentials.
For both of them a new claim claims is introduced as
claims: OPTIONAL. Object as defined in Appendix A.3.2 excluding the display and value_type parameters. mandatory parameter here is used by the Wallet to indicate to the Issuer that it only accepts Credential(s) issued with those claim(s).
I was wondering if this should be extended to also allow expected values inside the claim. This would allow the Wallet to signal expected claims which might help for cases where there are several options of the same type of credential to be issued.
A good example would be a bank where one user might be the owner of different bank accounts within that one bank and would like to get a credential for a specific one. This way authorization_details could be leveraged to signal the expected one.
We could introduce a new optional claim expected_value like this:
[
{
"type": "openid_credential",
"format": "vc+sd-jwt",
"vct": "SD_JWT_VC_example_in_OpenID4VCI",
"claims": {
"given_name": {
"expected_value": "SomeName"
}
}
}
]
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 Authorization Details sections for mdoc and SD-JWT VC, especially Appendix A.3.2, and compare the current claims definition with the proposed expected_value example. Done means resolving whether expected values belong in authorization_details and documenting the agreed claim semantics and constraints in the specification.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100