openid / openid/OpenID4VC-HAIP
Wallets must support the pre-auth flow
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 57
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Today many issuance flows start with the user in an authenticated state either in a website or native app. The issuer then wishes to issue a credential for that authenticated user. Currently this is done using the pre-auth code flow using short lived token.
For this to work we'd need to make the following changes to HAIP:
- Wallets MUST support both the auth code flow and the pre-auth code flow
- Issuers may choose to support either the auth code flow or the pre-auth code flow depending on their needs.
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 HAIP specification and locate the sections defining wallet and issuer authorization flows. Update the profile so the stated wallet and issuer requirements are represented consistently, then verify the specification's flow requirements and wording cover both authorization code and pre-authorization code flows.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100