Parametrized Backend Calls

[ACosaLinan]

Hi there,

I am currently exposing a service as an API at the url: http://backend-endpoint.com. The API documentation is found at http://backend-endpoint.com/api. For example the url to access an asset might be: http://backend-endpoint.com/{{id}}?param={{param}} where id and param represent a path segment and param respectively.

Following the documentation at https://international-data-spaces-association.github.io/DataspaceConnector/CommunicationGuide/v6/Parametrization#examples, a parametrized call (either path, parameters or both) seems to be possible.

Let's say:

• An artifact in my provider connector is added with the property accessUrl: http://backend-endpoint.com
• A resource in my provider connector is added with the property endpointDocumentation: http://backend-endpoint.com/api
• Artifact is added to a newly created representation, the representation is added to the artifact, ... (you know all these steps).

At this point, the provider is supposed to be ready to serve the service through the API. In order to cosume the service, after the contract agreement and get it registered as "request" in the consumer I am trying to access the resource by:

{{conector_consumer}}/api/artifacts/{{artifactConsumerId}}/data/{{id}}?param={{param}}&download=true&agreementUri={{agreementId}}

It returns an Response with code 417 Expectation Failed

{
"details": "{reason=https://w3id.org/idsa/code/INTERNAL_RECIPIENT_ERROR, payload=Could not retrieve data., type=class de.fraunhofer.iais.eis.RejectionMessageImpl}",
"message": "Failed to retrieve data."
}

The error is generated by the provider connector. See the logs in connector_provider_logs.txt.

I attach a Postman collection for reproducibility Dataspace Connector v6.0.0 Example for Github.txt as well.

I will appreciate any support.

Thanks very much in advance.

Kind regards,

Alejandro

NOTE: It works when the accessUrl is set to http://backend-example.com/{{id}}?param={{param}} and the asset is accessed from {{conector_consumer}}/api/artifacts/{{artifactConsumerId}}/data&download=true&agreementUri={{agreementId}}