1 Onboarding roles in Registry

1.1 Onboarding credential services for all entities

All entities request credential service from DA the Operator.

Actor	Utility Module
Provider	CREDENTIAL
Registrar	CREDENTIAL
Issuer	CREDENTIAL
Investor1	CREDENTIAL

Select ONBOARDING on the left navigation. In the Services box, click REQUEST CREDENTIAL USER SERVICE. (The User is different for each entity.)

../../_images/request_credential_user_service_1.png

A request is shown in the Requests box. The request is automatically accepted in the DevNet.

../../_images/request_credential_user_service_2.png

Now the credential service is created in the Services box.

../../_images/request_credential_user_service_3.png

1.2 Provider credential

DA as the Operator offers a credential to Provider. Provider accepts this credential offer.

Actor	Utility Module
Provider	CREDENTIAL

Select OFFERS on the left navigation. If there is a credential offer, click ACCEPT.

Then select CREDENTIALS on the left navigation, The onboarding credential for onboarding provider will be there.

1.3 Onboard Provider

Actor	Utility Module
Provider	REGISTRY

Select ONBOARDING on the left navigation. In the Services box, click REQUEST PROVIDER SERVICE. A request is shown in the Requests box.

A request is shown in the Requests box.

(Wait for acceptance by the Operator). Once accepted, a Provider Service is created.

Now Provider is onboarded as a Provider.

1.4 Onboarding requirements for registrars and holders

Here Provider specifies the credential requirement, i.e. what credentials are needed in order to be onboarded as a registrar or a holder.

Actor	Utility Module
Provider	REGISTRY

Select CONFIGURATIONS on the left navigation. In the Provider Configurations box, click CREATE PROVIDER CONFIGURATION.

../../_images/provider_configuration-1.png

A window pops up for input.

../../_images/provider_configuration-2.png

In this demo, the credential requirements are designed as following:

Role in Registry	Credential Requirements
Holder	[holder] [hasRegistryRole] [Holder]
Registrar	[holder] [hasRegistryRole] [Registrar]

Under Required Credentials for Holders, click ADD

In the Credential Issuers, paste the copied Provider’s Party ID
Then under Claim Requirements (where subject is the holder), click ADD
In Property, input hasRegistryRole
In Value, input Holder

../../_images/provider_configuration-3.png

Scroll down if needed

Under Required Credentials for Registrars, click ADD

In the Credential Issuers, paste the Provider’s Party ID
Then under Claim Requirements (where subject is the holder), click ADD
In Property, input hasRegistryRole
In Value, input Registrar

../../_images/provider_configuration-4.png

Then click CREATE. The provider configuration is created.

1.5 Provider offers Registrar credential

Provider offers a free credential to Registrar.

Actor	Utility Module
Provider	CREDENTIAL

Select CREDENTIALS on the left navigation. Click OFFER FREE CREDENTIAL. A window pops up for input.

Holder: Registrar’s Party ID
Id: registrar-registrar
Description: <anything>
Claims
- Subject: Registrar’s Party ID
- Property: hasRegistryRole
- Value: Registrar

../../_images/offer_registrar_credential-1.png

Click OFFER.

A credential offer is created. (Check OFFERS on the left navigation).

../../_images/offer_registrar_credential-2.png

1.6 Registrar accepts credential offer

Registrar accepts the credential offer as a Registrar.

Actor	Utility Module
Provider	CREDENTIAL

Select OFFERS on the left navigation. There is a credential offer from Provider.

../../_images/offer_registrar_credential-3.png

Click ACCEPT. Now a credential is created (Check CREDENTIALS on the left navigation).

../../_images/offer_registrar_credential-4.png

1.7 Provider offers Holder credential for Issuer, Investor1

Provider offers a free credential to Issuer, Investor1 (as Holders).

Actor	Utility Module
Provider	CREDENTIAL

Select CREDENTIALS on the left navigation. Click OFFER FREE CREDENTIAL. A window pops up for input.

Holder: Issuer’s Party ID
Id: issuer-holder
Description: <anything>
Claims
- Subject: Issuer’s Party ID
- Property: hasRegistryRole
- Value: Holder

Click OFFER.

Select CREDENTIALS on the left navigation. Click OFFER FREE CREDENTIAL. A window pops up for input.

Holder: Investor1’s Party ID
Id: investor1-holder
Description: <anything>
Claims
- Subject: Investor1’s Party ID
- Property: hasRegistryRole
- Value: Holder

Click OFFER.

Credential offers are created. (Check OFFERS on the left navigation).

1.8 Issuer accepts credential offer

Issuer accepts the credential offer as a Holder.

Actor	Utility Module
Issuer	CREDENTIAL

Select OFFERS on the left navigation. There is a credential offer from Provider.

../../_images/credentials_holders_accept-1.png

Click ACCEPT. Now a credential is created (Check CREDENTIALS on the left navigation).

../../_images/credentials_holders_accept-2.png

1.9 Investor1 accepts credential offer

Investor1 accepts the credential offer as a Holder.

Actor	Utility Module
Investor1	CREDENTIAL

Select OFFERS on the left navigation. There is a credential offer from Provider.

../../_images/credentials_holders_accept-3.png

Click ACCEPT.

Now a credential is created (Check CREDENTIALS on the left navigation).

../../_images/credentials_holders_accept-4.png

1.10 Registrar requests onboarding as a Registrar in the Registry

Registrar requests onboarding the Registry as a Registrar.

Actor	Utility Module
Registrar	REGISTRY

Select ONBOARDING on the left navigation. In the Services box, click REQUEST REGISTRAR SERVICE

A window pops up for input.

Provider: Provider’s Party ID

Click REQUEST.

A request is shown in the Requests box.

1.11 Provider accepts onboarding request from Registrar

Provider accepts the request.

Actor	Utility Module
Provider	REGISTRY

Select ONBOARDING on the left navigation. In the Services box, Provider sees the request.

Click ACCEPT.

Now Registrar is onboarded as a Registrar by the Provider.

1.12 Issuer requests onboarding as a Holder in the Registry

Issuer requests onboarding the Registry as a Holder.

Actor	Utility Module
Issuer	REGISTRY

Select ONBOARDING on the left navigation. In the Services box, click REQUEST HOLDER SERVICE

A window pops up for input.

Provider: Provider’s Party ID

Click REQUEST.

A request is shown in the Requests box.

1.13 Investor1 requests onboarding as a Holder in the Registry

Investor1 requests onboarding the Registry as a Holder.

Actor	Utility Module
Investor1	REGISTRY

Select ONBOARDING on the left navigation. In the Services box, click REQUEST HOLDER SERVICE

A window pops up for input.

Provider: Provider’s Party ID

Click REQUEST.

A request is shown in the Requests box.

1.14 Provider accepts onboarding requests from Issuer, Investor1

Provider accepts the requests.

Actor	Utility Module
Provider	REGISTRY

Select ONBOARDING on the left navigation. In the Services box, Provider sees the three requests.

../../_images/provider_accept_onboarding-1.png

Click ACCEPT for all requests

Now Issuer, Investor1 are onboarded as a Holder by the Provider.

../../_images/provider_accept_onboarding-2.png

1.15 All entities are onboarded

Check all entities are onboarded by Provider

Actor	Utility Module
Registrar, Issuer, Investor1	REGISTRY

Select ONBOARDING on the left navigation.

Registrar as Registrar

../../_images/provider_accept_onboarding-3.png

Issuer as Holder

../../_images/provider_accept_onboarding-4.png

Investor1 as Holder

../../_images/provider_accept_onboarding-5.png

Congratulations! The overall onboarding process in the Registry is complete. Now it is time to token specific activities.