transfer-01-negotiation fails to create a policy

[FlorianK13]

Bug Report

Describe the Bug

Creating a policy as described in transfer-01-negotiation: create a policy on the provider fails. It does not register a policy called aPolicy.

Other requests, like registering assets or creating a contract, are working fine.

Expected Behavior

Successfully set up a policy called aPolicy

Observed Behavior

Instead when I run curl -d @transfer/transfer-01-negotiation/resources/create-policy.json -H 'content-type: application/json' http://localhost:19193/management/v2/policydefinitions -s I get an HTTP 400 Error.

Steps to Reproduce

Steps to reproduce the behavior:

1. follow the steps from transfer-00-prerequisites

2. create an asset, as described in 1-create-an-asset-on-the-provider-side

3. run curl -d @transfer/transfer-01-negotiation/resources/create-policy.json -H 'content-type: application/json' http://localhost:19193/management/v2/policydefinitions -s

4. get this HTTP Error 400 page:

   <title>Error 400 Bad Request</title>

   HTTP ERROR 400 Bad Request

   URI:	/management/v2/policydefinitions
   STATUS:	400
   MESSAGE:	Bad Request
   SERVLET:	EDC-management

5. Meanwhile, the provider connector logs this error:

• jakarta.ws.rs.BadRequestException: Failed to expand JsonObject: There wa a problem encountered loading a remote context [http://www.w3.org/ns/odrl.jsonld]

Context Information

• OS: Windows
• openjdk 17 2021-09-14

Possible Implementation

As the create-policy.json file was recently changed (see here), maybe the error lies here?

[github-actions]

Thanks for your contribution 🔥 We will take a look asap 🚀

[ndr-brt]

hey, EDC is not officially supporting Windows OS, please run the sample in a posix machine.

specifically, there was an issue related to this problem: eclipse-edc/Connector#3687

[FlorianK13]

Yes, sorry didn't see that - now it works.

[bpetrovbg]

After hitting the same problem, I can also confirm that everything works fine under WSL2 :)