Unable to obtain credentials: Failed fetching catalog when using edc-ce-mds:7.2.1

[tsatardekar-deloitte]

Hello Team,

We are currently using edc-extensions for our MDS EDC Connector (ghcr.io/sovity/edc-ce-mds:4.2.1). As there is new release from edc-extensions, we want to use the latest 7.2.1.

There were several configuration changes we had to adapt to, for using the latest version. Now all the views (assets, contracts, transfer history) work fine. However for the Catalog browser, I see an error in the logs as below

org.eclipse.edc.spi.EdcException: Unable to obtain credentials: Server response to Request{method=POST, url=https://daps.test.mobility-dataspace.eu/token, headers=[Accept:application/json, Content-Type:application/x-www-form-urlencoded]} was not 200 but was 400: {"error":"access_denied","error_description":"No scopes granted"}

I followed the release-migration notes and added the below configurations

  EDC_OAUTH_PROVIDER_AUDIENCE: "idsc:IDS_CONNECTORS_ALL"
  EDC_OAUTH_ENDPOINT_AUDIENCE: "idsc:IDS_CONNECTORS_ALL"
  EDC_AGENT_IDENTITY_KEY: "client_id"
  MY_EDC_PARTICIPANT_ID: "my SKI:API key"

I referred to one similar question here where you advised to use version 4.2.1 for MDS. However this was back in December 2023, so I'm hoping now MDS is compatible with the new version.

Can you please guide me here?

Thanks,
Trupti

[tmberthold]

Hi and welcome,

the MDS provides a guide how to set up a MDS EDC with a pre-filled docker-compose and some more details for v7.2.1:
https://github.com/Mobility-Data-Space/mobility-data-space/wiki/2.-Step-(Configuration)-MDS-EDC

E.g. the technical meaning of the MY_EDC_PARTICIPANT_ID has changed, I think it will correspondend to the MDS-ID.

BUT I think currently on the MDS test-environment the required version is still v4.2.1.

@jkbquabeck correct me if I'm wrong here.

[tsatardekar-deloitte]

Thank you @tmberthold for your response.

Strange thing, when I visit the Mobility Data Space github repo, I see a different Wiki than the one you shared: https://github.com/Mobility-Data-Space/mobility-data-space/wiki/2.-Step-(Configuration).
So I had been referring an older one. As it was last updated in Dec 2023, I also assumed that now MDS might be compatible with 7.2.1.

We had created the connector certificates in somewhere around Aug 2023 and I don't remember having a MDS-ID there.
Also, if for MDS test-environment the required version is still v4.2.1, it will be hard to deploy 7.2.1 into prod without testing it in dev.

@jkbquabeck, do you more information into this?

[tmberthold]

Hi,
my linked wiki-page is the future version of MDS with a newer EDC CE version, yours is the currently still valid EDC CE v4.2.1.

[jkbquabeck]

Hi @tsatardekar-deloitte,
I am not the right person to share any details on the planning for MDS releases and migration.
Please reach out to MDS for concrete statements. For now, MDS productive and test environment require EDC v4.2.1.

[ip312]

Hi @tsatardekar-deloitte,

I answered you per mail. Please don't be confused with the new site, it is still work in progress and therefore not visible in the main wiki menu. You will soon receive an invitation to the customer event, where all the details and how-tos will be explained in detail.

[tsatardekar-deloitte]

Thank you for your email @ip312 :) We will wait for the customer event.