How wallet requests encrypted JAR from the Verifier?
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 112
- Forks
- 38
- Avg merge
- 12d 19h
- Merged PRs (30d)
- 4
Description
Under section 5.10 there is the following:
If the Wallet requires the Verifier to encrypt the Request Object, it SHOULD use the
jwksparameter within the wallet_metadata parameter to pass public encryption keys.
I have the impression that using jwks is not enough, because Verifier doesn't know which encryption method to use.
Perhaps there need to be either
request_object_signing_alg_values_supportedandrequest_object_encryption_enc_values_supportedas defined in JAR, orrequest_object_encryption_enc_values_supportedprovided that all jwks elements containalg.
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 section 5.10 of the OpenID4VP specification and compare its wallet_metadata and jwks guidance with the JAR requirements mentioned in the issue. Determine what encryption-algorithm metadata is needed, then document an agreed specification change and its required examples or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cryptography
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100