Make sure that all criteria are met as defined on the Admission part of the iSHARE Trust Framework.
If required, ensure availability of a certificate
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.
While generating/obtaining the certificate, a valid PartyID (EORI) 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 governance/agreements.
Capabilities url is an optional URL for parties providing services, referring to the Capabilities endpoint used to discover the participant's services.
Registrar Satellite ID - is the id of the satellite or dataspace onboarding the participant.
2. Adding the certificate
If a certificate is required (see above), upload the certificate and click 'Save'.
3. Add an Authorisation Registry and addidtional details
For parties with the role of Entitled Party, optionally an Authorisation Registry can be added.
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.
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 and for Satellite or Data Space Authority role, a Satellite Agreement is required.
