FAQ

Why can't I just use EDC Connector?

Unfortunately the Eclipse Dataspace Components Connector is not compatible with MDS central components. Therefore, we developed extensions which allow an interaction between the EDC and the MDS central components. Additionally, the MDS EDC Frontend provides several enhancements, necessary for MDS interaction.

What should the variable EDC_OAUTH_CLIENT_ID look like?

EDC_OAUTH_CLIENT_ID: 7X:7Y:...:B2:94:keyid:6A:2B:...:28:80

Postman collection

Use Postman and import the collection. Depending on your configuration changes, you need to adjust variables on collection MDV > Variables > Current Value. Please note, that api_key needs to be aligned with EDC_API_AUTH_KEY in the docker-compose.yaml

Can I run a connector locally and consume data from an online connector?

No, it is not possible. Either both connectors should run locally or both connectors should be online to exchange data.

Can I consume data from my own connector?

No, you need two connectors in the same environment to test the provider-consumer chain. However you can use the permanently available MDS connector as provider in the test environment (just insert the address https://mds-test-next-001.prod-sovity.azure.sovity.io/api/dsp in the field Catalog Browser/Connector Endpoint of your connector).

Can I change the MDS Id in my on-prem connector on-the-fly?

No. Especially if you are provider and already have successfully negotiated contracts. On-the-fly change of the MDS Id will cause inconsistencies. If you want to re-start your connector with a new MDS ID you have to clean up the deployment before (all containers, images, volumes shall be deleted).

Do you have any further questions?

Please don't hesitate to contact us via the MDS Support System