EDC UI - Catalogue browser gets 403 error

[tsatardekar-deloitte]

Hello Team,

I'm using EDC connector as a docker image for setting up EDC Connector in the Mobility Data Space. I have setup the connector & also the EDC UI. In the catalogue browser I'm facing the below error

In the network tab of the browser, this endpoint being called
https://xx/api/v1/management/catalog?providerUrl=https://XX/api/v1/ids/data&limit=10000000
and it gets the below response
[
{
"message": "org.eclipse.edc.spi.EdcException: Received an error from connector (https://XXX/api/v1/ids/data): 403 Forbidden",
"type": "BadGateway",
"path": null,
"invalidValue": null
}
]

As I'm using EDC as a docker image, it is hard for me to understand what is happening inside. It is only the Catalogue browser that fails. I'm able to create assets, policies & contracts without any problem.

Please guide.

Thanks,
Trupti

[richardtreier]

Hi,

the measure for a correctly set-up EDC is the contract negotiation working between your EDC and another publicly available EDC.

For requesting another connector's catalog your connector backend uses its protocol endpoint (backend:11003/api/v1/ids, https://your-connector/api/v1/ids) to talk to the other connector's protocol endpoint. Both these endpoints need to be available to each other with both HTTP and HTTPS. Communication will be secured by the DAPS.

The 403 should not be coming from the connectors themselves, but something blocking the requests between these protocol endpoints.

Due to the intricacies of debugging MS8 EDC deployments and how EDC-to-EDC communication breaks fast with misconfiguration, we are currently working on a more detailed deployment guide which will incorporate our experiences from deploying the EDC on multiple kinds of corporate infrastructures. It should be available by the end of this week or start of next week.

Please note, that creating policies, assets and contract definitions only proves that your UI has access to your backend's management API (backend:11002/api/v1/management, https://your-connector/api/v1/management).

[tsatardekar-deloitte]

Thank you for your response @richardtreier. It was the App gateway rules that were blocking the calls with requestURI containing ids/data. We had to find a workaround to move the edc connector + consumer to another kubernetes cluster. It works now. Although, it will be really helpful if the EDC logging can give detailed error messages.
In the meantime, we were able to initiate the transfer process & also receive data. After the transfer process is complete, in the consumer UI -> Transfer history shows process "complete". However, on the connector side in the UI, the transfer history shows "in-progress". I see the below logs in the connector pod

2023-09-04 14:22:21 MIMEEvent=START_MESSAGE 
2023-09-04 14:22:21 Closing the input stream. 
2023-09-04 14:22:21 Message body reader (class org.glassfish.jersey.media.multipart.internal.MultiPartReaderServerSide) is trying to close the entity input stream. Not closing. 
2023-09-04 14:22:21 Skipped the preamble. buffer len=2,899 
2023-09-04 14:22:21 MIMEEvent=START_PART 
2023-09-04 14:22:21 MIMEEvent=HEADERS 
2023-09-04 14:22:21 Content-ID=0 
2023-09-04 14:22:21 Got attachment for Content-ID=0 attachment=Part=0:null 
2023-09-04 14:22:21 MIMEEvent=END_PART 
2023-09-04 14:22:21 MIMEEvent=END_MESSAGE 
2023-09-04 14:22:21 Message body reader (class org.glassfish.jersey.media.multipart.internal.MultiPartReaderServerSide) is trying to close the entity input stream. Not closing. 

What could be going wrong here?

[richardtreier]

Hello @tsatardekar-deloitte, this is a known bug, unfortunately. This issue will be fixed once the MDS switches to EDC 0.3.0, which is currently planned not before January 2024.

[richardtreier]

Relevant issue regarding the open transfer processes: eclipse-edc/Connector#3334

[tsatardekar-deloitte]

Thank you for your reply. We will wait for the release then :)