Conversation
This PR highlights several issues with this flow: Collapsing the first and second enrollment flows as the user won't always know the difference. Enrollment was not credential based. DIDs are the primary response from a lookup. Digital Addresses were not passing through user cloud agent. I attempted to make as few changes as possible while addressing these issues.
|
|
||
| DAS->>DAS: ADIA-DA-005:Provision a Cloud Agent for User with HIDA | ||
| DAS->>Cloud Agent: ADIA-DA-001:Request to Create DAS_USER_ID for HIDA | ||
| DAS->>Cloud Agent: ADIA-DA-001:Request to Create DID for Issuer |
There was a problem hiding this comment.
This is about onboarding a user. The DID will have the user as subject, hence the Issuer will create a DID for the User - not for the issuer.
There was a problem hiding this comment.
This is the DID for the User to give to the Issuer. Each Issuer should get a unique DID for the user.
There was a problem hiding this comment.
for use by Issuer
There was a problem hiding this comment.
DAS_USER_ID = DID described elsewhere
There was a problem hiding this comment.
include note in DAS_USER_ID definition to include one DID per Issuer / Service Provider. _pk, _sk also in terminology.
There was a problem hiding this comment.
Reverted DID to DAS_USER_ID, terminology update pending.
| DAS -> DAS: Store [DA, TA_USER_ISSUER, DAS_USER_ID, DAS_USER_ID_PK] | ||
| DAS ->> +ARD: ADIA-DR-002: Enroll [DAS_USER_ID, HIDA, HomeDAS_ID] to notify about DA | ||
| DAS -->> Cloud Agent: ADIA-DA-001:DA Created | ||
| Cloud Agent ->> ARD: Present HIDA Enrollment Credential |
There was a problem hiding this comment.
Where do we define what a HIDA Enrollment Credential is? Is this new?
There was a problem hiding this comment.
Is this a Verifiable Credential or an authentication credential?
There was a problem hiding this comment.
HIDA Credential needed in terminology section. - VC issued to the user containing HIDA. HIDA Cred is Directory Credential of a specific type.
|
Updated flows. Update to related definitions pending. |
2 participants
This PR highlights several issues with this flow:
Collapsing the first and second enrollment flows as the user won't always know the difference.
Enrollment was not credential based.
DIDs are the primary response from a lookup.
Digital Addresses were not passing through user cloud agent.
I attempted to make as few changes as possible while addressing these issues.