Onboarding/Accessing DID Registries

[alenhorvat]

Objective:

• Most DID registries require users to onboard to get write access
• Process may be both DID-method and DID-method instance/implementation-specific

Can we define a generic flow (or flows) that cover most cases, are light for wallet providers and don't or minimally disrupt the current processes?

Proposal:

• Present two flows that would cover most of the cases
  • user is redirected to the onboarding page and all the onboarding-related operations are performed there
  • onboarding via API (example: btcr)
• The document would allow for other processes that cannot be covered in the 2 cases above

https://identity.foundation/did-registration/#didstatestate

[alenhorvat]

For the meeting discussion.

[peacekeeper]

This looks great @alenhorvat , I'll review and think through it more before the next meeting.

[alenhorvat]

Discussion topics/examples

• https://www.oauth.com/playground/index.html

Responses: (HTTP example)

• show UI as in oauth example
• 302 (redirect)

operations create/update/deactivate need an additional property "proof"