Additional options for wallet-provided nonces for PoP
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
On the DCP WG call on June 27th, we concluded that c_nonce is in fact optional. To mitigate the attack discussed here https://github.com/openid/OpenID4VCI/issues/19 without a c_nonce, several options were brought up and we agreed to create a dedicated issue for this.
Some options are:
ath(access token hash)jti(chosen by the wallet with enough entropy)nonce(keep nonce in PoP but allow wallet-generated nonces similar tojti; probably not a good idea because in some situations/policies a server might fail distinguishing betweenc_noncevalues and wallet-generated nonces in thenonceclaim)
(cc @David-Chadwick @Sakurann @jogu @bc-pi @babisRoutis)
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
This issue names no repository files, tests, or implementation entry points. Start by reading the linked OpenID4VCI issue and the June 27 DCP WG discussion, then compare the ath, jti, and wallet-generated nonce options against the c_nonce attack. Done means an agreed protocol option and clearly specified normative changes.
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
- Needs clarification
- Newbie friendliness
- 25/100