-
Notifications
You must be signed in to change notification settings - Fork 1
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.
EDC_OAUTH_CLIENT_ID: 7X:7Y:...:B2:94:keyid:6A:2B:...:28:80
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
No, it is not possible. Either both connectors should run locally or both connectors should be online to exchange data.
No, you need two connectors in the same environment to test the provider-consumer chain.
As data consumer you can use the permanently available MDS connector as data 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).
As data provider with on-prem connector you can additionally request a CaaS in the same environment and use this CaaS as consumer connector.
As data provider with CaaS you need support from another MDS participant who already has a connector in the same enivronment or support from the MDS. In the last case please open the ticket with an exact description what should be tested.
No. Especially if you are provider and already have successfully negotiated contracts. On-the-fly change of the MDS Id (MY_EDC_PARTICIPANT_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).
Please don't hesitate to contact us via the MDS Support System
- Home
- User guide
- Useful information