FraunhoferISST / DataspaceConnector

This is an IDS Connector reference implementation.
https://www.isst.fraunhofer.de/de/geschaeftsfelder/datenwirtschaft/technologien/Dataspace-Connector.html
Apache License 2.0
103 stars 83 forks source link

Accessing artifact's data after rebooting a data consumer connector #488

Closed ctoscano-eu closed 3 years ago

ctoscano-eu commented 3 years ago

When using v6.0.0: 1-DataApp A linked to Connector A: creates a resource offer with contract, rule, representation, and one artifact. 2-DataApp B linked to Connector B: DataApp B asks Connector B to retrieve metadata from Connector A and to contract the Offer created above. He is then able to retrieve the artifacts data.

As expected, if the DataApp B reboots, it continues to have access to the contracted artifacts, via: POST .../api/artifacts/27beab9c-43c4-47c4-a3e3-43f98e55a27e/data Connector B continues to allow the DataApp to access the data.

However, if the Conector B is rebooted, the above step fails on the POST when accessing the very same artifact's data: 417 EXPECTATION_FAILED Body: {"details":"{reason=https://w3id.org/idsa/code/BAD_PARAMETERS, payload=Invalid transfer contract for requested artifact., type=class de.fraunhofer.iais.eis.RejectionMessageImpl}","message":"Failed to retrieve data."}

ctoscano-eu commented 3 years ago

Connector A is presenting this exception: io.dataspaceconnector.exception.ContractException: The issuer connector does not correspond to the signed consumer.

ctoscano-eu commented 3 years ago

My testing environment is the following: -DataApp A and Connector A run in a virtual machine -DataApp B and Connector B run in a different virtual machine -Each Connector has a certificate issued by AISEC

ctoscano-eu commented 3 years ago

thank you @juliapampus , I just confirmed in my test environment that the problem was solved.