[S2S]: Ratify Credential Provisioning flow
Open
Nobody has claimed this yet.
server-to-server
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Issue tracking consensus on the credential provisioning flow. Text is currently as follows:
- CredentialInstanceIds are returned from the 'credential/provision' endpoint after successful verification
- 'credential/get' is called per CredentialInstanceId, with an array of 'presentationKeys' and relevant proofs.
- The Wallet Server performs the fan out for multiple CredentialInstanceIds
- Asynchronous gets are handled by returning PENDING and recalling the endpoint later
- Credential Metadata can be returned from the 'get' endpoint OR retrieved independently from the 'credential/metadata' endpoint.
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 reviewing the credential/provision, credential/get, and credential/metadata flows described in the issue, including the handling of PENDING responses and multiple CredentialInstanceIds. The work is done when the project reaches and records consensus on one credential provisioning flow.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100