cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Unable to deploy iFlow in Integration Suite for AzureStorage List Blobs

oliverkrafft
Discoverer
0 Likes
784

Hi all,

we have tried to connect our azure blob storage via iflow and the azure storage adapter version 1.0.4 with the function list blobs. During deployment we receive the following error message:

[CONTENT][CONTENT_DEPLOY][RuntimeError] : {"message":"EXCEPTION","parameters":["org.apache.camel.FailedToCreateRouteException: Failed to create route Process_1 at: >>> To[sap-it-azure-storage:foo?receiverContainerName=aussendienstfiles&pageSize=200&receiverAccountName=stouvreisekosten&receiverResponseFormat=default&processInPages=false&sasToken=st=2024-08-22T07:53:12Z&se=2099-08-22T15:53:12Z&si=SAP Read Delete&spr=https&sv=2022-11-02&sr=c&sig=VQsEY6cnmX9XZoCTwmW1Y0iEK3I8eXVWctC2l6u0mI4%3D&receiverAuthorization=SASTOKEN&timeOut=60000&blob=ListBlobs&requestHeaders=x-ms-blob-type=blockblob] <<< in route: Route(Process_1)[[From[direct:test_azure_TimerEventDefinitio... because of Failed to resolve endpoint: sap-it-azure-storage://foo?blob=ListBlobs&pageSize=200&processInPages=false&receiverAccountName=stouvreisekosten&receiverAuthorization=SASTOKEN&receiverContainerName=aussendienstfiles&receiverResponseFormat=default&requestHeaders=x-ms-blob-type%3Dblockblob&sasToken=st%3D2024-08-22T07%3A53%3A12Z&se=2099-08-22T15%3A53%3A12Z&si=SAP+Read+Delete&sig=VQsEY6cnmX9XZoCTwmW1Y0iEK3I8eXVWctC2l6u0mI4%3D&spr=https&sr=c&sv=2022-11-02&timeOut=60000 due to: Failed to resolve endpoint: sap-it-azure-storage://foo?blob=ListBlobs&pageSize=200&processInPages=false&receiverAccountName=stouvreisekosten&receiverAuthorization=SASTOKEN&receiverContainerName=aussendienstfiles&receiverResponseFormat=default&requestHeaders=x-ms-blob-type%3Dblockblob&sasToken=st%3D2024-08-22T07%3A53%3A12Z&se=2099-08-22T15%3A53%3A12Z&si=SAP+Read+Delete&sig=VQsEY6cnmX9XZoCTwmW1Y0iEK3I8eXVWctC2l6u0mI4%3D&spr=https&sr=c&sv=2022-11-02&timeOut=60000 due to: There are 6 parameters that couldn't be set on the endpoint. Check the uri if the parameters are spelt correctly and that they are properties of the endpoint. Unknown parameters=[{se=2099-08-22T15:53:12Z, si=SAP Read Delete, sig=VQsEY6cnmX9XZoCTwmW1Y0iEK3I8eXVWctC2l6u0mI4=, spr=https, sr=c, sv=2022-11-02}]"],"childMessageInstances":[{"message":"CAUSE","parameters":["org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: sap-it-azure-storage://foo?blob=ListBlobs&pageSize=200&processInPages=false&receiverAccountName=stouvreisekosten&receiverAuthorization=SASTOKEN&receiverContainerName=aussendienstfiles&receiverResponseFormat=default&requestHeaders=x-ms-blob-type%3Dblockblob&sasToken=st%3D2024-08-22T07%3A53%3A12Z&se=2099-08-22T15%3A53%3A12Z&si=SAP+Read+Delete&sig=VQsEY6cnmX9XZoCTwmW1Y0iEK3I8eXVWctC2l6u0mI4%3D&spr=https&sr=c&sv=2022-11-02&timeOut=60000 due to: Failed to resolve endpoint: sap-it-azure-storage://foo?blob=ListBlobs&pageSize=200&processInPages=false&receiverAccountName=stouvreisekosten&receiverAuthorization=SASTOKEN&receiverContainerName=aussendienstfiles&receiverResponseFormat=default&requestHeaders=x-ms-blob-type%3Dblockblob&sasToken=st%3D2024-08-22T07%3A53%3A12Z&se=2099-08-22T15%3A53%3A12Z&si=SAP+Read+Delete&sig=VQsEY6cnmX9XZoCTwmW1Y0iEK3I8eXVWctC2l6u0mI4%3D&spr=https&sr=c&sv=2022-11-02&timeOut=60000 due to: There are 6 parameters that couldn't be set on the endpoint. Check the uri if the parameters are spelt correctly and that they are properties of the endpoint. Unknown parameters=[{se=2099-08-22T15:53:12Z, si=SAP Read Delete, sig=VQsEY6cnmX9XZoCTwmW1Y0iEK3I8eXVWctC2l6u0mI4=, spr=https, sr=c, sv=2022-11-02}]"],"childMessageInstances":[{"message":"CAUSE","parameters":["org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: sap-it-azure-storage://foo?blob=ListBlobs&pageSize=200&processInPages=false&receiverAccountName=stouvreisekosten&receiverAuthorization=SASTOKEN&receiverContainerName=aussendienstfiles&receiverResponseFormat=default&requestHeaders=x-ms-blob-type%3Dblockblob&sasToken=st%3D2024-08-22T07%3A53%3A12Z&se=2099-08-22T15%3A53%3A12Z&si=SAP+Read+Delete&sig=VQsEY6cnmX9XZoCTwmW1Y0iEK3I8eXVWctC2l6u0mI4%3D&spr=https&sr=c&sv=2022-11-02&timeOut=60000 due to: There are 6 parameters that couldn't be set on the endpoint. Check the uri if the parameters are spelt correctly and that they are properties of the endpoint. Unknown parameters=[{se=2099-08-22T15:53:12Z, si=SAP Read Delete, sig=VQsEY6cnmX9XZoCTwmW1Y0iEK3I8eXVWctC2l6u0mI4=, spr=https, sr=c, sv=2022-11-02}]"]}]}]}

The following settings are stored in the adapter:

oliverkrafft_0-1724316661815.png

oliverkrafft_1-1724316709954.png

In addition, we have adhered to the following blog https://community.sap.com/t5/technology-blogs-by-members/steps-to-access-azure-blob-storage-via-rest...

Unfortunately we could not find any hint in the logging on azure side, why we get this error.

Do you have any ideas as to what the problem might be and how we can solve it?

Thanks a lot and best regards,

Olli

 

Accepted Solutions (1)

Accepted Solutions (1)

Willem_Pardaens
Product and Topic Expert
Product and Topic Expert
0 Likes

In the Connection tab, the Alias should reference the credential (secure parameter) for the SAS token you created before, not the actual SAS token.

oliverkrafft
Discoverer
0 Likes
Thanks for the info. In the blog it seems more like an optional function and not a mandatory one. It works with this change
Willem_Pardaens
Product and Topic Expert
Product and Topic Expert
0 Likes
Ok great, this is more like a security best-practice to not put credentials directly in your flows, but manage them centrally and securely. You will see this concept in multiple places in Integration Suite.

Answers (0)