Is it possible to send customized body and auth headers on the proxy on transfer-06-consumer-pull-http sample?

[skarampatakis]

Hi, I have a question in regards of the transfer-06-consumer-pull-http sample. After the recent update I see that you can specify on the HttpAddress object the proxyBody, proxyQuery etc elements which will further customize the query send to the original data provider. On the end of the README you note that it is possible to add a proxyPath without being specified on the HttpAddress, so it is customizable when the request is done. Is it possbile to do the same with the proxyBody, proxyMethod and proxyQuery?

Additionally, in the case the basuUrl is protected by Basic Auth, is it possible to specify the Auth header that will be passed on the original server? There is already the Authorization header, but if I get it correctly, this is used by EDC internally and never passed to the remote data server.

Thank you very much in advance.

[github-actions[bot]]

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

[xdxxxdx]

Same question here.

[github-actions[bot]]

This issue is stale because it has been open for 14 days with no activity.

[ndr-brt]

Hi, the proxy properties in the HttpData DataAddress are booleans that, when set to true will permit to have the body, method and query from the consumer request to be proxied to the provider data source.

For authentication, in the DataAddress you can set the authKey (header name) and the authCode (the token value). You can have it stored in the vault, in that case you need to use secretName instead as the key with which the secret is stored in the vault.

[skarampatakis]

Thanks a lot @ndr-brt, I ended up to this conclusion as well, but forgot to update the ticket. This is the request I used to create the asset:

curl -d '{
           "@context": {
             "edc": "https://w3id.org/edc/v0.0.1/ns/"
           },
           "asset": {
             "@id": "assetId",
             "properties": {
               "name": "product description",
               "contenttype": "application/json"
             }
           },
           "dataAddress": {
             "type": "HttpData",
             "name": "Test asset",
             "baseUrl": "http://localhost:8081/",
             "proxyPath": "true",
             "proxyBody": "true",
             "proxyQueryParams": "true",
             "proxyMethod": "true",
             "authKey": "Authorization",
             "authCode": "Basic xxx"
           }
         }' -H 'content-type: application/json' http://localhost:19193/management/v2/assets \
         -s | jq

I am not sure how I could use the vault. Is there any documentation you could point me to?
Additionally, I m not sure how this could work in case I have another backend ie another service? Would I then need to create an additional data plane on the consumer side, ie repeating steps in scenario 6 from 2 till the end, modifying the required properties?

Thanks a lot in advance!

[ndr-brt]

the Vault depends on the implementation that you are using, e.g. in the samples the FsVault is used, and there's a file where you can store your secrets, if are using an HashiCorp instance, it has both a UI and an API to store secrets.

if you have another backend service you don't need another data-plane, you just need to adjust the "dataAddress" accordingly