Case Sentive issue while using Create SAS URI by path (V2) in Logic app

VShivam 6

Hi I tried to use Create SAS URI by path (V2) for generating the SAS token URL to the file that is stored in the Blob storage.

I have used the triggerOutput field as shown below

But when the WebURL is generated the url is generated ignoring the case sensitivity and I am not able to download the file with the generated WebURL link.

Please let me know how can I get the exact URL when the output filed "List of Files Id is used"

1 answer

MayankBargali-MSFT 68,746 Reputation points

2021-09-13T06:54:26.453+00:00

@VShivam It looks like you are using When a blob is added or modified (properties only) (V2) trigger as I can see it returns the List of files blob meta data and using this output in your create sas uri by path (v2). Please confirm if my understanding is correct. If this is the case then create sas uri by path (v2) accepts the blob path where as you are passing the List of Files Id. You need to pass List of Files Path i.e. Path parameter that has the path of the file or folder of BlobMetadata.
Please sign in to rate this answer.

1 person found this answer helpful.
VShivam 6 Reputation points

2021-09-13T09:08:22.28+00:00

Thanks for the update @MayankBargali-MSFT

We have used this parameter "List of files path" it is giving us the complete file path including the folders that are stored in the Blob when WebURL is generated.

But as per our requirement we should not show the file path , so instead I tried to generate the SAS URI with List of Files Id, as a result I got the URL as below which is in accessible

https://xxxxxxxxxxxxxxxxx.blob.core.windows.net/jtjmbmv3y28taw52b2ljzxmtymlsbgluzyuyzm91dhb1dcuyzk5ldytnawnyb3nvznqrv29yzcteb2n1bwvudcstk0nvchkrkdiyks5kb2n4?sv=2018-03-28&sr=c&sig=8LWqYODUdgVk2lKG0kwldGuaqNjhSaDWDNEh6Xw91WA%3D&st=2021-09-13T08%3A53%3A48Z&se=2021-09-13T08%3A58%3A48Z&sp=r

So do we need to use only List of Files Path i.e. Path parameter instead List of Files Id in that case Logic app execution should be failed as the URL generated is not a valid one

I

MayankBargali-MSFT 68,746 Reputation points

2021-09-14T05:46:18.877+00:00

@VShivam The action creates the SAS URI for the blob path not to the SAS URI of the container or to the storage account.
If your requirement is that once the SAS URI is generated you want to access all the blob inside that container that it is not possible using this action. If the SAS URL is generated for the path test/abc.txt then you can only access abc.txt file under that test path. You cannot use the same SAS URL to access another file in the same path i.e. test/xyz.txt In case you are caccessing xyz then you will get AuthenticationFailed error as the token URI was generated for abc.txt and not for xyz.txt

In case you want to generate the SAS URL at the container level then you need to leverage the Storage SAS REST API to generate the SAS token using HTTP action.

Hope this clear things up. Feel free to get back to me if you have any queries or concerns.

MayankBargali-MSFT 68,746 Reputation points

2021-09-14T06:14:24.957+00:00

@VShivam The Create SAS URL by path (v2) creats SAS link for a blob using the path and not at the container. The SAS URL generated by this action will only valid for the blob for which it was created and not for other containers/blobs. If you tried to use the same SAS link then you should get the AuthenticationFailed error.

If your requirement is that you want to generate the SAS token and used it for all blobs/contaniors level then you need to use Storage REST API to generate the token using HTTP triger.

If you still want only the SAS signature without the path/blob name then you can use substring to get your desire string format. But as I aleady mentioned that this SAS is only valid for the blob for which it was created and not for other containers/blobs.

Yashas Manjunath 26 Reputation points

2023-02-09T08:53:10.89+00:00

@MayankBargali-MSFT Thanks for the info this helps me too. But the SAS URL created from this process is different and I am still getting errors when opening the file using the link (Shared access signature).

I have observed that the link I get when I generate the SAS URL from the UI (which works) is different from this link I get from the logic app action. Please assist.

End goal: to just send the link of the file by email. instead of generating it from the UI and copy-pasting the link.

Yashas Manjunath 26 Reputation points

2023-02-14T00:01:01.7133333+00:00

Got the answer. The group policy identifier should have been kept empty.
Sign in to comment