IMPORTANT: This a functionality that needed to be included in the version v2.0.0 (included in the documentation) from the DPP however was posponed for v2.1.0
Because of data compliance the user needs to be able to "sign" or "agree" the contract and be able to choose which policy he wants to accept.
In case there are more than one policy the application uses to take the first one. However that can cause problems when the Policies contain agreements that can not be fellfield by the user.
What we want to achieve with this PR?
We want to add a "policy selection" feature to the application so that the user can say which policy he wants to choose.
We want to allow the backend to handle more than one policy and more contracts for data soverenighty.
Allow the frontend to handle the new changes without loosing its functionality.
What is new?
Added
Added policyId parameter to "/agree" api.
Added mechanism to get a policy by id from a catalog contract
Added frontend logic to call the "/decline" and "/cancel" backend APIs
Added reload option in case of error
Added/fixed logging of the Digital Twin Registry Contracts and which policy was selected (Data Souverenighty improve)
Added util method to move files from one path to another
Added functionality to treat more than one policy and more than one contract, allowing user to decide
Added safety functionalities to make sure that the contract selected is correct.
Update
[BRAKING CHANGE] Renamed API "sign" to negotiate "/agree"
Bumped Vite to version >=4.5.2
Updated the frontend to allow the "AutoSigning" of contracts.
Optimized temporary directory logging of the DTR negotiation
Issues Fixed
Fixed issue related to "sleepy" EDCs, allowing the backend to re-request the contract negotiation when the EDC does not respond.
Why we create this PR?
Because of data compliance the user needs to be able to "sign" or "agree" the contract and be able to choose which policy he wants to accept.
In case there are more than one policy the application uses to take the first one. However that can cause problems when the Policies contain agreements that can not be fellfield by the user.
What we want to achieve with this PR?
We want to add a "policy selection" feature to the application so that the user can say which policy he wants to choose. We want to allow the backend to handle more than one policy and more contracts for data soverenighty. Allow the frontend to handle the new changes without loosing its functionality.
What is new?
Added
Update
Issues Fixed