[S2S]: Back-channel Credential Offer
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
The current specification (as with Canonical VCI) leaves back-channel (i.e from the Issuer Server to the Wallet Server) out of scope of the specification. This is tracking if this is a feature we want. To enable this, we would need to define an endpoint on the Wallet Server for Credential Offers, and there would need to be some common linking mechanism between the Issuer and Wallet to identify the same User to give the offer to (e.g. account identifier).
This is potentially useful, if available as it provides a secure cross-device channel for credential offers.
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
The issue names no repository files, tests, or entry points. Start by reviewing the current OpenID4VCI specification and the referenced Canonical VCI scope, then determine whether back-channel Credential Offers should be supported. Done would require an agreed endpoint and a common Issuer–Wallet user-linking mechanism, if the feature is accepted.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100