๐Ÿ’ปiREC 5 Demo UI Guide

Demonstrating Multi User Role functionality

This folder contains a sample file that is referenced in the Demo Guide

  1. New iREC Policy (IRec Policy 5 group (1707126709.066208559).policy)

1.The Guardian reference implementation comes with two predefined users:

  1. Standard Registry

  2. Participant

  3. Approver

2. After running the installation commands, open a tab on your browser and navigate to http://localhost:3000/. Typically, the way we start the reference implementation demonstration is by logging in as Standard Registry. Click the Demo Admin Panel drop-down located in the upper right-hand corner of the login screen and select Standard Registry user.

3. You will now be prompted to configure your Standard Registry account. Press the Generate button to generate a Hedera Operator ID and an Operator Key and enter the details of your Standard Registry. Press Connect when finished. This will now create Hedera Consensus Service Topics, fill the account with test hBar, create a DID document, create a Verifiable Credential, etc.

4. This could be one of the most interesting parts of the reference implementation. Now we will be creating the Policy. We have two ways to "create policies." The first way is to import an existing policy. This is the easiest way to get started. When you import a policy, all schemas and tokens that are required in the policy are automatically populated. To do this, you can use the sample policy that we have already uploaded to IPFS by entering the Hedera Message IDs.

iREC 1 : 1707125172.156394003
iREC 2 : 1707125414.999819805
iREC 3 : 1707126011.005978889
iREC 4 : 1707126227.976010003
iREC 5 : 1707126709.066208559
IRec Policy 6 search documents : 1707128237.926630472
IRec Policy 7 split documents : 1707130249.448431277
IRec Policy 8.1 MBP : 1707130450.268901183
IRec Policy 8.2 MBP : 1707130781.567041003
IRec 9 Module : 1707132260.399505507

Once clicked on OK, we have an option to Preview the Policy before importing it.

Once Policy is imported successfully, you have two options : 1. to publish the policy, 2. To run the policy in Dry Run mode.

Let's click on Publish button to publish the Policy to Hedera network.

5. Click on Standard Registry's profile icon and select "Log Out." We will now go back into the Admin Panel. This time we will select Registrant.

6. Now, we can click on the Policies tab. This is where the specific actions required by the Policy Workflow will be found. We can click the Open button to the right of the iREC Policy, the Standard Registry created. This is where the custom user will be able to assign the role that was created by Standard Registry during the workflow creation process. In our case, we created the custom role of Registrant so the user will need to select the Registrant role from the drop down.

7. Now, we create a group by selecting Registrant in the Dropdown. or we enter an invite link of the group received to join that particular group in the Accept invitation option.

8. Once Registrant option is selected from the dropdown, we get Group label field enabled. Group label can be given anything of our choice. Here, we are giving as Registrant Group for testing purpose.

Once, Group label is entered, we click on OK button.

9. Now we enter the Registrant Application details and click on Ok.

Once Submitted, Registrant waits for the approval of the application by Approver.

10. Next step is logout as Registrant and login as Approver. This can be done by selecting Installer from the Admin panel and then selecting Standard Registry from the dropdown in Profile tab.

11. Once Profile is created, we click on Policies tab and click on Go to view the Policy.

12. Same as Registrant, you have an option to create group or accept invitation. But, the only difference over here is you need to select Approvers option in the group dropdown.

13. Once Approver is created, now we get an option to Sign/Decline the Registrant application.

Note: If there are multiple approvers, we would need minimum of 70% consensus to reach the final result for an application.

14. In our demo, I will create 2 more approvers (Approver1 and Approver2) by following the above Step 12.

15. As there are 3 approvers, I would need minimum signatures of 2 approvers to reach the final decision (either signed or declined).

16. When one of the approver, signs or declines the application by clicking on Sign button, we get the progress bar of the result as shown below

To get complete information on the status, we need to click on "i" icon

17. For demo purpose, we will also sign the above application as an Approver by logging in as an Approver and following the step 15.

18. Once, minimum of 2 approvers sign the application, Registrant application is signed successfully.

19. Now, we login back as Registrant and click on Create New Device.

20. Device Registration details needs to be filled and submitted.

Once details are submitted, Registrant waits for the approval.

21. Now, we login back as Approver1 and approves the device created by Registrant. Device is approved by clicking on Sign button.

22. We logout as an Approver1 and login as Approver2 and approve the device by following step 21.

23. Once, two approvers approve the device, the device is approved successfully. Now, we log back in as Registrant.

24. Now, the Registrant creates an Issue Request by clicking on Create Issue Request.

25. Issue Request is created by entering the details as shown below.

26. Once the Issue Request is submitted, the request status can be checked by clicking on Issue Requests tab.

27. Now, we login as Approver1 and go to Issue Requests tab and click on Sign button to approve the Issue Request. We can also view the document by clicking on View Document button.

28. We will logout as Approver1 and login as Approver2 and follow same steps as Step 27.

29. Once, Issue Requests is being approved by minimum of 2 approvers, it is approved successfully.

30. Now we login as Registrant and can check the Token History by clicking on Token History tab.

31. To view TrustChain, we logout as Registrant and login as Standard Registry and click on View TrustChain.

Last updated