Negotiation fails

[Akshay-a-j]

Hi,

I am integrating Sovity edc-extensions into two different systems, experiencing negotiation failure in one system, whereas it is successful in another. Please refer to the following log for your consideration

ContractNegotiation: ID fcd3b1e3-48c6-4416-8198-30a29f0156ad. Fatal error while [Consumer] Send ContractRequestMessage message. Error details: {"@type":"dspace:ContractNegotiationError","dspace:code":"400","dspace:reason":"Contract offer is not valid: Invalid consumer identity","@context":{"dct":"https://purl.org/dc/terms/","edc":"https://w3id.org/edc/v0.0.1/ns/","dcat":"https://www.w3.org/ns/dcat/","odrl":"https://www.w3.org/ns/odrl/2/","dspace":"https://w3id.org/dspace/v0.8/"}}

Thank you

[Akshay-a-j]

Hi @tmberthold,
Could you please look into the above mentioned problem and let us know how to resolve the issue?

[tmberthold]

For a general understanding of when in the process which message is sent from which connector to the other: In this case, the error occurs right at the beginning of the negotiation process, in the ContractRequestMessage that the consumer sends to the provider.

According to the logs, the actual error message corresponds to: Contract offer is not valid: Invalid consumer identity

Unfortunately, this error is not documented or has already occurred (and then been documented, e.g. in a GItHub Issue or Discussion).
Since I haven't encountered this error yet too and it is not documented/occured somewhere, I have to examine the edc-core code to see where this error message could come from.

I will share my trip:

• The error message itself comes from here in the code: Link
• According to the code, this error happens only when the Participant Agent attribute PARTICIPANT_IDENTITY is not set at all, which is the verified identity of the participant: Link
• There is an explanation in the class of what the PARTICIPANT_IDENTITY attribute stands for and that it is required to be set: Link
• The explanation includes: The default behavior is to set the identity using the client_id claim, if present.

Which version of the sovity EDC CE is used? What kind of IAM system do you use (Omejdn DAPS, KeyCloak DAPS, etc.)?
There have been changes in this area that require manual adjustments, e.g. with sovity EDC CE v6.0.0 and using the Omejdn DAPS.

[Akshay-a-j]

@tmberthold thank your quick response. We are currently utilizing version 6.0.0. The negotiation process is encountering issues following recent modifications made within the last 7 days. A few weeks ago, I cloned the repository, and it was functioning properly. However, upon cloning it again today, the negotiation process is now unsuccessful.

[tmberthold]

Sorry, I have one two more questions so we can narrow this down:

• Could you also provide information about where the EDC gets the DATs from, i.e. whether you have a connection to an Omejdn DAPS, a KeyCloak DAPS or something similar?
• What is the goal? Is it just setting up a local demo or are you trying to join an existing dataspace?

[Akshay-a-j]

I'm unfamiliar with Omejdn DAPS or KeyCloak DAPS since I'm relatively new to this domain. Currently, our focus is on setting up a local demo to explore the process of creating multiple assets and policies for efficient data sharing.

[Akshay-a-j]

sure, thank you

[Akshay-a-j]

@tmberthold Apologies for any inconvenience. I'm checking if the problem has been resolved. If not, is there an alternative method within Sovity-UI for transferring files?

[tmberthold]

For all other CE versions you would need a DAPS connection to get a DAT for exchanging messages, no other version uses an IAM-mock, for example the MDS-DAPS if you are part of the Mobility Data Space, or a locally running DAPS environment. However, for a possible Omejdn DAPS connection I would suggest CE 4.2.1. For Keycloak DAPS, you can go with v5.0.0 or v6.0.0 (current new ones at the time of writing)

[tmberthold]

Update: The issue will be resolved in the upcoming EDC CE DEV v7.0.0