Implement fix for Connector-Restricted-Usage Policy not working since EDC CE v5.0.0 about edc-extensions HOT 3 CLOSED

This issue has been introduced when new PolicyScopes have been added to the core-EDC.

These PolicyScopes are evaluated on incoming and outgoing dsp calls. For the incoming dsp calls this has not been an issue, because the counterParties identity can be fetched from the incoming token into a ParticipantAgent. On the other side there is no counterParty token available for outgoing requests.

To circumvent this issue, the registration of the policy has been changed. It is no longer registered for all scopes, but just for contract.negotiation and catalog scopes, such that this policy is evaluated for contract negotiation and retrieving the catalog, but not on a dsp-request level.

from edc-extensions.

@efiege as aligned during today's daily, as your highest prio please implement the fix for this gap. Some important points:

• after you analyse the problem and plan a solution for it, please add your effort estimation (number of work days needed to implement fix) to the "Story Points" field
• at the latest we want the fix to be implemented by Wednesday 14.02 so that we can ship out the fix in Raze release on Thursday 15.02 because we need to respect the M600 deadline for MDS 2.0. If your effort estimation exceeds this date, please contact me on Teams ASAP.
• we agreed at daily today that we will test the topic manually because the E2E tests we want to implement during the scalability bootcamp will not be ready in time. Please contact @richardtreier to get the sample tests he has related to this topic.

As needed, please contact me on Teams wherever I can support you more.

from edc-extensions.

is working, I fell into a trap

from edc-extensions.