Participant Onboarding

[zeier]

After agera-edc/IdentityHub#13, agera-edc/MinimumViableDataspace#58, and agera-edc/MinimumViableDataspace#24

Description

A new dataspace participant should be able to deploy its connector and register with the dataspace in order to participate as a new participant in the dataspace.

This deployment and registration will be done after the initial deployment of the dataspace (see agera-edc/MinimumViableDataspace#139)

It shall be possible to perform deployment and onboarding in individual steps, to be able to demo the different steps involved in participant onboarding.

The current MVD pipeline performs the following steps for initial deployment (once features agera-edc/IdentityHub#13, agera-edc/MinimumViableDataspace#58, and agera-edc/MinimumViableDataspace#24 are implemented):

• Deploys a simulated GAIA-X authority (local filesystem private key, and public web DID document)
• Deploys Dataspace authority (DID document and RegistrationService)
• For each participant:
  • Deploys EDC (contains IdentityHub)
  • Pushes signed Gaia-X Verifiable Credential to Identity Hub
  • Pushes unsigned region Verifiable Credential to Identity Hub
  • Calls RegistratioService to onboard participant

To deploy and onboard an additional participant, the following steps are required:

• A manually triggered pipeline in MVD deploys a (non-onboarded, empty) participant and publishes the participant DID private key
• User can download GAIA-X Authority private key, checkout and compile the Identity Hub CLI, and use it to sign a GAIA-X Membership Verifiable Credential and push it to the participant's Identity Hub
• User can download the participant's private key, checkout and compile RegistrationService CLI, and use it to onboard the participant

Acceptance Criteria

• [ ] The components for a new participant can be deployed, the participant is not onboarded yet
• [ ] Onboarding can be performed in a subsequent step
• [ ] A demo can be done showing that the participant has been onboarded (e.g. catalog is populated with items from other participants)
• [ ] Deployment and onboarding actions can be performed based on step by step instructions
• [ ] Documentation for participant deployment and onboarding steps is available

Stories

• [ ] agera-edc/MinimumViableDataspace#158
• [ ] agera-edc/MinimumViableDataspace#159
• [ ] agera-edc/MinimumViableDataspace#160
• [ ] agera-edc/MinimumViableDataspace#161

[zeier]

Put on hold since capacity until end of sprint 13 is projected to be insufficient to cover this feature. Can be taken up as the next priority feature if capacity is available.