DAPS URL authentication Issue from EDC

[devopscaxsol]

Hey ALl,

when I am trying to request to my EDC like

https://demo.com/v2/catalog/request

I am getting error like as below

2025-02-11 10:40:28 HTTP client exception caught for request Request{method=POST, url=https://dev-daps.demo.com/realms/master/protocol/openid-connect/token, headers=[Accept:application/json, Content-Type:application/x-www-form-urlencoded]}
org.eclipse.edc.spi.http.EdcHttpClientException: Server response to [POST, https://dev-daps.demo.com/realms/master/protocol/openid-connect/token] was not 200 but was 401: {"error":"invalid_client","error_description":"Invalid client or Invalid client credentials"}

What are steps we can consider to resolve this scenario?

[tmberthold]

Hi,
this reminds me of this discussion, please check if your EDC is known in the DAPS and all config settings of the EDC and DAPS are properly set: #1100 (reply in thread)

Public Backend Config Docu:
https://edc-ce.docs.sovity.de/community-edition-deployment/production#edc-backend-configuration

[devopscaxsol]

HI,

yes configured like the way mentioned. but when we request URL as above mentioned getting ERROR.

in my config i am using DAPS URL like,

EDC_OAUTH_TOKEN_URL: 'https://xxxxxx/realms/master/protocol/openid-connect/token'
EDC_OAUTH_PROVIDER_JWKS_URL: 'https://xxxxxx/realms/master/protocol/openid-connect/certs'

can you please share your thought is this wrong or right ?

[devopscaxsol]

HI @tmberthold

I am trying to hit catalog api request like

https://demo.com/api/management/wrapper/ui/pages/catalog-page/data-offers?connectorEndpoint=https://demo.com/api/dsp

i am getting error logs like ,

Caused by: org.eclipse.edc.spi.EdcException: Unable to obtain credentials: Server response to [POST, https://daps-demo.com/realms/master/protocol/openid-connect/token] was not 200 but was 401: {"error":"invalid_client","error_description":"Invalid client or Invalid client credentials"}

can you please guide help me here.

[tmberthold]

Since this is a config problem EDC <-> DAPS hidden somewhere in one of your components forcing the DAPS to reply that he doesnt recognize the EDC, here are example settings for a DAPS client, e.g. using ski-aki as client-id:

[devopscaxsol]

thanks for sharing this. let me go through this.

[devopscaxsol]

@tmberthold

I have followed approach u have guided, But still I am getting error while hitting catalog api request.

ERROR I am getting in EDC logs,

Caused by: org.eclipse.edc.spi.EdcException: Unable to obtain credentials: Server response to [POST, https://demo-edc.demo.com/realms/master/protocol/openid-connect/token] was not 200 but was 400: {"error":"invalid_client","error_description":"Unable to load public key"}

Please suggest.

Thanks

[tmberthold]

@devopscaxsol

You have moved forward from "Invalid client or Invalid client credentials" to "Unable to load public key", so your DAPS now finds the client it is looking for but doesnt find the public-certificate-key of the client to validate its incoming DAT request. The public key is required to verify incoming requests. If no or an incorrect public key is configured under the Keys tab of the client in the DAPS, this may result in this issue.

Please validate if you have placed the public key of the client/EDC in the DAPS keys tab.

[devopscaxsol]

Hey @tmberthold

Thanks for suggestions.

I have added key.

I am getting error in my daps side when I am hitting catalog api request, {{CONSUMER_EDC_MANAGEMENT_URL}}/wrapper/ui/pages/catalog-page/data-offers?connectorEndpoint={{REQUESTING_DSP_ENDPOINT}}

ERROR is

2025-02-14 05:25:51 JerseyExtension: Unexpected exception caught
de.sovity.edc.utils.catalog.DspCatalogServiceException: {"@type":"dspace:CatalogError","dspace:code":"401","dspace:reason":"Token validation failed.","@context":{"dct":"https://purl.org/dc/terms/","edc":"https://w3id.org/edc/v0.0.1/ns/","dcat":"https://www.w3.org/ns/dcat/","odrl":"http://www.w3.org/ns/odrl/2/","dspace":"https://w3id.org/dspace/v0.8/"}}
at de.sovity.edc.utils.catalog.DspCatalogServiceException.ofFailure(DspCatalogServiceException.java:25)

Please suggest in this.

Thanks

[tmberthold]

Hello and thank you for the additional information, I've forwarded this internally.

[tmberthold]

Hello - to address your questions more efficiently, we would be happy to set up a short call with you.
If you're open to this, please provide an email address where we can send an invitation and clarify the rest.

In the meantime, it would also be helpful if you could share a bit more context regarding your use case. Specifically:

• What business scenario are you trying to solve?
• In which industry do you work?
• Is your usage of sovity services for a research purpose or a for-profit business role?
• How did you learn about sovity’s GH community?
• (If not already mentioned) What pain points are you experiencing with sovity's service?

Your insights will help us better understand your needs and provide the best possible support. Looking forward to your response.

Best

[tmberthold]

Thanks for sharing the details, have forwarded them internally.

[tmberthold]

Thank you again for reaching out and for your patience.

After further internal discussions, we unfortunately have to inform you that sovity does not support DAPS as a stand-alone component as you seem to do. To use the DAPS, it must be integrated and used together with the DSPortal.

Given this internal decision, we regret to inform you that the previously offered meeting will not take place, as we are unable to offer further support for this specific request. Please understand that this was not my personal decision, and I truly regret that we cannot provide the assistance you were hoping for.

I appreciate your understanding and wish you success with your project.

[devopscaxsol]

OK. you are referring this https://github.com/sovity/dataspace-portal? @tmberthold