Trying to Create and Add a New Consumer to the K8S Cluster

[susef]

Hello everyone!

I've been trying for a while to deploy an additional connector in the MVD scenario. Without going too deep into context, I attempted to add a new one to the scenario, but I encountered an error. To simplify the test, I reduced it to simply renaming consumer to consumer2.

To do this, I refactored all occurrences in the MVD directory, replacing consumer with consumer2. However, even with this simple test, I still get the same error.

Everything starts up correctly, the pods are deployed properly, and it seems that all connectors can communicate. I begin by registering the two participants (provider and consumer2) in their respective Identity Hubs, but I get an "Unauthorized" error in the Consumer2 Control Plane. When I check the logs of the Catalog Server, I see that it is trying to find a did:web:consumer-identityhub%3A7083:consumer even though nothing is deployed under the name consumer.

Attached are two images corresponding to the error being discussed.

This post is intended to ask two things:

• General question related to the main objective: Can additional connectors be deployed in the scenario? How could this be done?
• Specific question regarding the error: Where is the Catalog Server configured to look for the DID of consumer instead of consumer2? I couldn't find any reference to this in the repository, at least after searching for quite some time.

I hope to find some guidance in this forum.
Thank you in advance!

Joseba

ERROR IN consumer2-controlplane:

ERROR IN provider-catalog-server:

[paullatzelsperger]

i transferred the discussion here.

if you want to deploy additional connectors you will have to:

• pre-populate the new participant's identityhub
• create, sign and issue verifiable credentials to it
• seed data to it (Assets, policies, etc.)
• add its DID to the TargetNodeDirectory (cf. https://github.com/eclipse-edc/MinimumViableDataspace/?tab=readme-ov-file#81-catalog-node-resolver)

in a nutshell: yes, it can be done. no, there is no step-by-step guidance at this time.

Before you attempt this, I strongly recommend to fully understand DSP and DCP first, and dig through the documentation of EDC and MVD.

[susef]

Hi!

Thanks for your quick response!

I believe the steps you mentioned are already being followed. The first step, registering the participants in the Identity Hub, is done using the seed-k8s.sh script, after refactoring consumer to consumer2.

The next step you mentioned, managing the Verifiable Credentials, is done manually using a script that mimics the behavior of the JwtSigner.java test. These credentials should be functional since they have been tested with the original consumer and provider scenario (without modifications).

The seed data step is not necessary, as the error we are encountering occurs when registering the connectors in their respective Identity Hubs, right before using the Postman collection to interact with them.

Finally, the deployment is executed after adding both participants (consumer2 and provider) to the JSON documents inside the /assets/participant folder.

By investigating the control planes of the connectors, we can see that they correctly register the list of participants. See the following images:

CONSUMER2 CONTROL PLANE:

MANUFACTURING CONTROL PLANE:

QNA CONTROL PLANE:

I am not sure why this error occurs, where the Catalog Server is searching for the DID of consumer when only consumer2 exists.

Additionally, I will follow your advice to better understand DSP (Data Space Protocol) and DCP (Decentralized Claims Protocol). However, any extra help would be greatly appreciated.

Many thanks and best regards,

Joseba

[paullatzelsperger]

A 401 means, that there is some authentication error along the way. MVD is provided "as-is" and unfortunately we can't provide 1:1 coaching or debugging. If you have specific questions you are more than welcome to ask them, but this is too unspecific and wide-scoped. Closing.