Handling of notification which are revoked from receiver side because of policy expiration

[ds-jleyh]

As dev
I want a proper concept how to implement policy expiration in notification process
so that I have clear vision what and how to implement this stuff

Link

• related to [POLICY] Implement handling of notification which are revoked from receiver side because of policy expiration #639

Hints / Details

• Inside the library irs-edc-client ContractNegotiationService method startNewNegotiation starts the negotation including the necessary policy check.
• The "policy checker" checks if policy permissions matches and policy is expired (validUntil is before currentDataTime).
• If one of the checks fails, a UsagePolicyException is thrown and has to be handled by the requestor
• UsagePolicyException should provide the reason why the policy is not matching (Mismatch because of missing policy or mismatch because of policy expired)
• In case notification process fails because of a policy mismatch which is indicated by a UsagePolicyException this should be shown to the user in a sufficient way.

1. Extension for org.eclipse.tractusx.irs.edc.client.policy.PolicyCheckerService to provide reason why policy is not valid. e.g. UsagePolicyPermissionException and UsagePolicyExpiredException
2. Notification process ends with UsagePolicyPermissionException or UsagePolicyExpiredException this is shown to the user in a sufficient way in frontend
3. Clarify with devs how UsagePolicyException is handled now in the code

Acceptance Criteria

• Concept for Handling of notification which are revoked from receiver side because policy expires covers
  • User is aware of policy expiry on frontend side
  • system provides a suitable error message why the asset is not accessible

Out of Scope

• Further activities on handling of assets with expired policy

[jzbmw]

@mkanal isn't that something already in work?

[mkanal]

@jzbmw no there is nothing in progress.

[mkanal]

@ds-crehm PR review is done. There are some remarks. Please check

[ds-crehm]

@ds-alexander-bulgakov, please review. Thanks!

[ds-alexander-bulgakov]

No obscurities could be found, the concept is ready for PO-review. FYI @jzbmw

[ds-crehm]

Implemented by #656