You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating an asset it is possible to add additional headers to be passed to the Datasource endpoint.
For this purpose, in the create asset request, we added an x-api-key header and set its value to peanutbutter so that the https://w3id.org/edc/v0.0.1/ns/dataAddress field looks like this:
Using this created asset, and following the rest of the steps in the postman collection, we managed to start the data push.
Our Datasource endpoint was hit correctly, however, the x-api-key header was not received.
Expected Behavior
Upon transfer, we expect the additional headers to arrive to the Datasource endpoint.
Observed Behavior
Upon transfer, no additional headers arrived to the Datasource endpoint.
Send the rest of the requests in order: 2 Create Simple Policy, 3 Create ContractDefinition, 5 Start Negotiation, 6 Request Contract Agreements
Get the contract agreement @id from the response of 6 Request Contract Agreements and paste it in the Body of 7 Start Data Push replacing the value of https://w3id.org/edc/v0.0.1/ns/contractId.
Send the 7 Start Data Push request
Check your Datasource server logs, where the x-api-key header is missing from the received request.
Context Information
Used version
edc: ghcr.io/sovity/edc-dev:5.0.0
edc-ui: ghcr.io/sovity/edc-ui:2.0.0
OS: Linux
Possible Implementation and Work Breakdown
This is possibly a regression since it was working with the following versions:
edc: ghcr.io/sovity/edc-ce-mds:4.1.0
edc-ui: v0.0.1-milestone-8-sovity12
The text was updated successfully, but these errors were encountered:
Bug Report
May be related to (consider solving all related items in one instance):
Description
When creating an asset it is possible to add additional headers to be passed to the Datasource endpoint.
For this purpose, in the create asset request, we added an
x-api-key
header and set its value topeanutbutter
so that thehttps://w3id.org/edc/v0.0.1/ns/dataAddress
field looks like this:Using this created asset, and following the rest of the steps in the postman collection, we managed to start the data push.
Our Datasource endpoint was hit correctly, however, the
x-api-key
header was not received.Expected Behavior
Upon transfer, we expect the additional headers to arrive to the Datasource endpoint.
Observed Behavior
Upon transfer, no additional headers arrived to the Datasource endpoint.
Steps to Reproduce
Steps to reproduce the behavior:
PROVIDER_EDC_SOURCE_URL
to a simple server that prints the headers of all requests it receives. We used this gist.1 Create Asset
, then Body and add the following inside thehttps://w3id.org/edc/v0.0.1/ns/dataAddress
field:2 Create Simple Policy
,3 Create ContractDefinition
,5 Start Negotiation
,6 Request Contract Agreements
@id
from the response of6 Request Contract Agreements
and paste it in the Body of7 Start Data Push
replacing the value ofhttps://w3id.org/edc/v0.0.1/ns/contractId
.7 Start Data Push
requestx-api-key
header is missing from the received request.Context Information
Used version
ghcr.io/sovity/edc-dev:5.0.0
ghcr.io/sovity/edc-ui:2.0.0
OS: Linux
Possible Implementation and Work Breakdown
This is possibly a regression since it was working with the following versions:
ghcr.io/sovity/edc-ce-mds:4.1.0
v0.0.1-milestone-8-sovity12
The text was updated successfully, but these errors were encountered: