Extension point for additional verifier-supplied information
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
OpenID4VP defines the verifier_info extension point (see https://openid.github.io/OpenID4VP/openid-4-verifiable-presentations-1_0-wg-draft.html#section-5.1-2.12.1) that allows ecosystems to convey additional information about the request or the verifier. We currently seem to be missing such a defined extension point with the current/initial proposal.
To provide a bit of context on verifier_info on how it is currently used: For EUDI Wallets, that extension point is used to convey the registered intended use - right now in the form of a JWT signed by the registrar, that guarantees that a request received by the Wallet is inside the intended use/scope registered in the ecosystem by that entity.
(from comments on #1)
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 by reading the linked OpenID4VP section 5.1-2.12.1 and the context from issue #1, then compare that extension point with the current or initial DCHP proposal. Done means the proposal defines how verifier-supplied information, including the described intended-use context, can be conveyed.
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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100