Wallet Selection Binding during Issuance
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Building up on the problem described in https://github.com/w3c-fedid/digital-credentials/issues/382.
We had a discussion at IIW, and integration for the following option 3 into VCI seems to be preferred by the DCP WG at the moment:
The Issuer could provide a binding key when making the create call. Here the platform would pass the wallet hmac(binding_key, selected_wallet_identifier)
Implementing Option 3 in VCI will most likely mean the following (https://github.com/w3c-fedid/digital-credentials/issues/382#issuecomment-3434365368):
send platform attestation containing hashed origin at Token/PAR Request
define a claim for origin in wallet attestation
issuer needs to compare origins
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 issue 382 and its referenced comment, then review the VCI Token/PAR request and wallet attestation areas. Determine how Option 3 should cover platform attestation, the origin claim, and issuer origin comparison; the work is done when those requirements are specified and integrated into VCI.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100