As a dataspace participant I want to have my policies enforced to ensure that my assets are only used for the intended purpose.
This story is for spiking on the components needed to implement only a simple, static rule, that the caller identity has a claim "region=eu"
Acceptance Criteria
[x] Follow up issues are created to allow implementing the scenario (see story agera-edc/MinimumViableDataspaceFork#95 )
[x] The follow up issues, when implemented, would have a scenario automatically tested such as: one provider, one consumer with region=eu and one consumer with region=us. An asset negotiation with one consumer fails, with the other it succeeds
Feature agera-edc/MinimumViableDataspaceFork#137
Description
As a dataspace participant I want to have my policies enforced to ensure that my assets are only used for the intended purpose.
This story is for spiking on the components needed to implement only a simple, static rule, that the caller identity has a claim "region=eu"
Acceptance Criteria
Tasks