Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Profile page Endorser DID registration handling #1052

Merged
merged 8 commits into from
Apr 11, 2024

Conversation

loneil
Copy link
Collaborator

@loneil loneil commented Apr 2, 2024

Enhance the Register DID function on the Tenant UI Profile page to cover additional Endorser governance processes we use for BC Gov Traction.

Need to split the Register DID (depending on use case) steps into multiple asynchronous as the Endorser will have to multiple manual steps in some cases. Add additional checks and handling to move on to the next step automatically for various auto-endorsement cases.

So with the existing cases, these governance setups are supported in the Tenant UI.

I think we should possibly make documentation/videos showing how all these options work...

Case 1: "Auto-everything" Endorser

  • Tenant UI has a specific ledger flagged as "Quick Connect"
  • This is the Sandbox and PR use case with the Tools Endorser we currently use
  • Just click the 1 ledger select and because connection and endorsement is auto it will just progress through the steps
  • If Quick Connect is not specified things are still auto completed but user will refresh and continue manually (but everything still finishes automatically)

Case 2: Approve Connection, set connection to auto endorse

  • This case is where the Endorser has to approve the connection manually
  • But then the Endorser sets that connection configuration to auto-endorse
  • Tenant UI user makes connection request
    • Tenant sees pending connection
    • Endorser approves that connection at some point
    • Endorser sets connection to auto-endorse
    • Tenant comes back and can Register DID
    • DID registration continues automatically

Case 3: Approve Connection, set DID in allow list

  • Endorser has to approve the connection manually
  • But then the Endorser will wait until the published DID is given to them, and set it on the Allow list
  • Tenant UI user makes connection request
    • Tenant sees pending connection
    • Endorser approves that connection at some point
    • Tenant comes back and starts the DID registration, they see the "candidate" public did
    • They communicate that DID to the endorser
    • Endorser adds DID to allow list, Endorser Service moves on and approves transactions for that DID
    • Tenant comes back and can continue Register DID process

In order for the Tenant UI Profile page to know the DID registration is In Progress in case 3 it needs to scan through it's pending author transactions (likely always just the 1 going for Tenant setup) to see which "candidate DID" the tenant communicates to the Endorser.

@loneil loneil changed the title Profile page DID handling (WIP) Profile page DID handling Apr 3, 2024
@loneil loneil changed the title Profile page DID handling Profile page Endorser DID registration handling Apr 9, 2024
@loneil loneil force-pushed the feature/tenantUiEndorseDidHandling branch from 279b850 to 60132d4 Compare April 9, 2024 21:07
Signed-off-by: Lucas ONeil <lucasoneil@gmail.com>
Signed-off-by: Lucas ONeil <lucasoneil@gmail.com>
Signed-off-by: Lucas ONeil <lucasoneil@gmail.com>
Signed-off-by: Lucas ONeil <lucasoneil@gmail.com>
Signed-off-by: Lucas ONeil <lucasoneil@gmail.com>
Signed-off-by: Lucas ONeil <lucasoneil@gmail.com>
Signed-off-by: Lucas ONeil <lucasoneil@gmail.com>
Signed-off-by: Lucas ONeil <lucasoneil@gmail.com>
@loneil loneil force-pushed the feature/tenantUiEndorseDidHandling branch from 60132d4 to ba1265d Compare April 10, 2024 20:46
@loneil loneil merged commit 1ef10d2 into main Apr 11, 2024
11 checks passed
@loneil loneil deleted the feature/tenantUiEndorseDidHandling branch April 19, 2024 23:53
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.

2 participants