using a VC for Verifier Attestation
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 112
- Forks
- 38
- Avg merge
- 12d 19h
- Merged PRs (30d)
- 4
Description
the core idea is: "Verifier obtains a VC from a trusted third party, a VC includes a key material of a Verifier, authorization request is signed using that key". need to define a schema for that VC.
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 #372 and review its stated Verifier Attestation flow. Define the VC schema needed to carry Verifier key material and support signing authorization requests; done means the schema is specified clearly enough for the OpenID4VP project to implement or review.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100