search

International-Data-Spaces-Association / DataspaceConnector

This is an IDS Connector reference implementation.
Apache License 2.0
35 stars 29 forks source link

Error at Usage logging policy #38

Open jfernandezsqs opened 2 years ago

jfernandezsqs commented 2 years ago

I have deployed two Dataspace connectors version 7.0.1 and configured them to point to my local Clearing House. After the contract negotiation I obtain the data as expected. The issue comes when I delete the logging of the Dataspace connectors to the Clearing House. This is changing application.properties file of the DSC to:

## Clearing House
##clearing.house.url=XXX
##clearing.house.path.process=process
##clearing.house.path.log=messages/log

According to the documentation (https://international-data-spaces-association.github.io/DataspaceConnector/Documentation/v6/UsageControl#policy-patterns) image I should not be able to access and obtain the data after the contract negotiation because the DSC's are not logged to the clearing house. Executing this scenario I am obtaining the data from connector acting as provider. As far as I understand from the documentation this should not be like this and I should not obtain the data.

HeinrichPet commented 2 years ago

Currently, the clearing house configured in the consumer is used to log the data usage. Instead, it should be defined on the provider side to which clearing house the data usage should be logged. For this, it would have to be ensured before or during contract negotiation that this clearing house can be reached by the consumer, so that the policy can be enforced at the consumer. All in all, the whole policy must be implemented anew.

Simply throwing an exception and blocking the data usage wouldn't solve the problem.

We currently not plan to reimplement that feature, but are open for contribution.