Skip to content

Conversation

@TelegramSam
Copy link
Contributor

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.

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
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the DID for the User to give to the Issuer. Each Issuer should get a unique DID for the user.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for use by Issuer

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DAS_USER_ID = DID described elsewhere

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

include note in DAS_USER_ID definition to include one DID per Issuer / Service Provider. _pk, _sk also in terminology.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where do we define what a HIDA Enrollment Credential is? Is this new?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a Verifiable Credential or an authentication credential?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

HIDA Credential needed in terminology section. - VC issued to the user containing HIDA. HIDA Cred is Directory Credential of a specific type.

@rlin1 rlin1 added this to the WD01 milestone May 26, 2021
@TelegramSam
Copy link
Contributor Author

Updated flows. Update to related definitions pending.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants