Data-Transfers are possible when provider changed his MDS-ID

tmberthold commented 1 month ago

Description - What happened? *

If the provider with the MDS ID XXX has a contract, which is successfully negotiated, and then changes the MDS ID to YYY on-the-fly without deleting the database it is further possible for the consumer to consume the data and the asset presentation and the contract history present the new (wrong) MDS ID YYY.

Expected Behavior *

Data transaction shall be not possible due to the wrong MDS Id on the provider side.

Observed Behavior *

Data transaction are still possible if provider MDS ID changed.

Steps to Reproduce

Start the on-prem provider connector with MDS ID XXX and create a contract offer with always free policy.
From the consumer side: negotiate the offer.
From the provider side: Change the MDS Id in the docker compose to YYY and re-start the connector without deleting the database
From the provider side: Check that the MDS Id in the contract offer is changed to YYY
From the consumer side: Try to consume the data. It is further possible.

Context Information

No response

Relevant log output

No response

Screenshots

No response

AbdullahMuk commented 1 month ago

Issue is caused because of core EDC 0.2.1 limitations and the scenario described is an edge-case. Will be fixed when migrating to core EDC 0.6.x (or higher).

/cc @jkbquabeck @tmberthold

AbdullahMuk commented 4 weeks ago

Issue is caused because of core EDC 0.2.1 limitations and the scenario described is an edge-case. Will be fixed when migrating to core EDC 0.6.x (or higher).

/cc @jkbquabeck @tmberthold

@ip312 given the description of the causes, can we align that this issue will not be fixed within the current MDS CaaS based on core EDC 0.2.1 but rather it will be fixed when migrating MDS CaaS to core EDC 0.6.x (or higher)?

sovity / edc-ce