Participant Management

(Adding Participants on the Participant Registry UI)

This page explains how a Participant can be added to the Participant Registry.

1. Fill out participant details

Adding Participant Details

Participant details

While generating/obtaining the certificate, a valid PartyID is also required. This PartyID or identifier is used to register the participant in the dataspace. The party name is the Organisation Name used to generate/obtain the certificate. Adherence status should be active for participants that are in compliance with the dataspace agreements. Capabilities url is an optional URL for parties providing services, referring to the Capabilities endpoint used to discover the participant's services. Registrar Data Space ID - is the ID of the dataspace onboarding the participant.

2. Adding the certificate

If a certificate is required (see below), upload the certificate and click 'Save'.

Certificates addition in the Participant Registry

3. Add an Authorisation Registry and additional details

For parties with the role of Entitled Party, optionally an Authorisation Registry can be added.

Adding Additional Details

AR & additional details

Authorisation Registry and Additional Participant Details are optional.

4. Add agreements and add the party to the right dataspace

Add two agreements (Terms of Use and Accession Agreement) and optionally extra agreements that are specific for a data space.

Adding Agreements

Agreements

The signed Terms Of Use and Accession Agreement are required for all participants. Dummy agreements can be added for test environment.

For Certified Parties - Certified Parties agreement is required.

For more information on the Legal agreements required for onboarding participants to a dataspace, refer to the Legal Agreements in the Trust Framework.

5. Add party roles

Select the roles which the participant will fulfill.

Adding Roles

Roles

A minimum of one role is required to be added. Organisation or Participants can also play multiple roles.

For clarity on Roles used in the Trust Framework, refer here.

For all participants with the role of Service Provider, Service Consumer with machine-to-machine API implementation, Authorization Registry or Identity Provider a certificate is required.

• For production implementations refer to iSHARE's eSEAL Guide.
• For UAT/test implementations refer to creating a test certificate.