Id for HttpProxy

[hlange]

Hi,

I currently working on the "Data Plane Transfer Sync" and I was looking for an Id that the DataSource is receiving that is matching the request to the contract.

I couldn't find any Id that could be used for this. Is the idea that this should be handled by a service outside of the EDC?

Best regards,
Henrik

[ndr-brt]

Hi, what do you mean with "the request to the contract"?
To pass parameters to the DataSource within the data-plane-http extension (I'm guessing you are talking about http endpoints), please take a look at the extension documentation

[hlange]

Yes, but this is a bad solution:

1. I could send this information also in the body however, this means that the consumer need to add this information manually, this can be done wrong, intentionally or not
2. This information exists like you mentioned in the EDR and also in DataRequest Object when using Data Plane Transfer Client so why not forward this without the possibility of human error
3. Will be needed for the federation service Sovereign Data Exchange, so it should exist by design

[jimmarino]

Which side is the "DataSource" on, the provider, i.e., you are issuing the request directly to the provider's data plane? If so, I don't think the contract id should be passed by the consumer and trusted by the provider. An authorization header is passed and that can be used to correlate the contract id.

[hlange]

@jimmarino I think you understand my problem. Regarding your last sentence, exist such header currently, and I didn't saw it, or should it exist and is currently not available?

[tom-rm-meyer-ISST]

I was wondering about that too. The authToken of the EDR (issued to the consumer) contains the information to validate the access via the data plane. This header is not passed to the provider's dataAsset.dataAddress.baseUrl endpoint.
Issuing the cid could allow a provider (when receiving the proxy request) to map this request to the contract and e.g. enforce policies that are not enforceable by the connector itself.

Additionally, I'm wondering if it would be beneficial to be able to route through DAPS information. E.g. in Catena-X I would be able to receive verified partner identification data I would otherwise need to pass through a header / body as a consumer, which is somewhat contradictionary to the trust provided by the connector.

[jimmarino]

The EDR token contains the CID as a claim, see ConsumerPullTransferTokenDecorator.