Daps Token Fetching v5.0.0

[ptriantis-ubitech]

Hello Community,

With the latest release v5.0.0 it seems that when requesting the Token from the DAPS, the body of the request does not contain the scope key-value pair. So the DAPS returns a 400 response instead with error description: No scopes granted.

Is the removal of the aforementioned key-value desired/expected?

Thank you!

[bearn01d]

With the IDS Multipart protocol being replaced now, the oauth2-daps extension is required for having the scope requested. See https://github.com/eclipse-edc/Connector/tree/main/extensions/common/iam/oauth2/oauth2-daps.

[ptriantis-ubitech]

Hi, firstly I would like to thank you for your immediate response.

I've found that extension also, but according to this, the MDS Community Edition, supports DAPS authentication. How does the DAPS authentication happens without the extension that adds the scope? I mean shouldn't MDS Community Edition already contain the extension mentioned? Or, the DAPS used doesn't require a scope maybe?

Thanks in advance.

[bearn01d]

As I'm not working at sovity, I don't know whether the DAPS used by them requires the scope. To get the MDS CE connector working in your setup right away, you could rebuild the image with this extension added. But for the general question, I unfortunately don't know the answer.

[ptriantis-ubitech]

Yeah it's more a general question because the previous versions had the scope in the request, so i wanted to know if this was an intentional change. Thanks again for your answer!

[tmberthold]

Hi!
If you're trying to get connected to the MDS with the sovity CE, please follow their list of compatible versions for their ecosystem, e.g. currently sovity EDC CE v4.2.1 should be the right choice (not the newer one v5.0.0 or v6.0.0):
https://github.com/Mobility-Data-Space/mobility-data-space/wiki/Current-and-planned-MDS-components-versions#current-mds-components-versions-mds-release-12-01112023