verifier authentication
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
The strawman seems to be silent on how to authenticate the verifier to the wallet - ie what corresponds to JAR+client_id validation in OpenID4VP. Probably something based on COSE_Sign1. Needs to support pluggable trust management. Needs to bind the encryption keys to the verfier backends somehow (trust).
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 strawman and comparing its verifier authentication gap with OpenID4VP JAR and client_id validation. Work out how COSE_Sign1, pluggable trust management, and encryption-key binding to verifier backends should fit together. Done means the authentication and trust model is specified clearly enough to implement.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100