ADL Gen2 rename using Path REST API failure with SAS token

Anil 1

Hi,

I am currently trying to rename a file within a container using the https://learn.microsoft.com/en-us/rest/api/storageservices/datalakestoragegen2/path/create API and an account-level SAS token. The SAS token was generated from the Azure portal with full access:

Services: Blob and File
Resource: Service, Container and Object
Permissions: R, W, D, L, A, C

While I can perform operations like List Paths and Create Path, I am unable to perform a rename operation. The operation fails with

AuthenticationFailed","message":"Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature

I am appending the SAS token obtained from the Azure portal to both the request URL and the value (file rename source path) of the "X-ms-rename-source" header. Could someone provide insights as to why the request keeps failing?

Thanks,
Anil.

Anil 1 Reputation point

2020-08-03T17:26:25.677+00:00

Request made:

PUT https://{accountName}.{dnsSuffix}/{filesystem}/{path}?timeout=90&<sasTokenFromAzurePortal>

Headers:

Accept: application/json, application/octet-stream
Content-Type: ""
X-ms-rename-source: /{filesystem}/{path}?<sasTokenFromAzurePortal>
X-ms-version: 2018-06-17
Accept-Charset: utf-8
User-Agent:
MartinJaffer-MSFT 26,046 Reputation points

2020-08-03T22:54:57.673+00:00

@Anil Thank you for bringing this issue to our attention. I have reproduced the problem, and will reach out internally for more information.
Anil 1 Reputation point

2020-08-20T20:24:38.123+00:00

Hi @MartinJaffer-MSFT ,

Do we have any updates on this issue?

Thanks,
Anil.
MartinJaffer-MSFT 26,046 Reputation points

2020-08-25T00:42:19.467+00:00

My apologies, @Anil . While I intitially got acknowledgement, my follow-ups have been like a black hole; without response.
Today, I sent one final follow-up with that lead, and worked closely with a new lead. It is looking like this might be a product bug.

I was given recommendations to try Service SAS instead of Account SAS, and use Azure CLI to generate the tokens. May I show you how to use that while I push this case internally. My apologies for dropping the ball on this, you must be frusterated.

If you prefer the Account SAS and do not want to wait any more, you can raise a support ticket. If you do not have a support plan, I can give you a 1-time free support ticket. If you want to go the support ticket route, send me an email at AzCommunity@Microsoft.com . Please include: this thread URL, Your subscription ID. Including my name in the subject line will help me find the email.

My searches of similar cases show people switching to OAuth instead.
Anil 1 Reputation point

2020-08-25T03:43:08.11+00:00

Hi @MartinJaffer-MSFT ,

Thanks for reverting. I forgot to mention in the thread that it did not work with service SAS either. I had generated service SAS tokens from Azure CLI as well. So the issue still remains irrespective of an account SAS or service SAS. I would like to go to the support ticket route. Thanks for providing information regarding the subscription. I just realized I have opened a ticket with my personal email ID and not the company's email ID. Can I check if we have a company subscription ID? If yes, can I use this thread URL along with that ID to open a support ticket?
OR do I open a completely new support ticket with the company's subscription ID?

Could you guide me with this?

Thanks,
Anil.
MartinJaffer-MSFT 26,046 Reputation points

2020-08-25T23:53:13.76+00:00

Hi @Anil . The most important part is the Azure Subscription ID. Once you have that, you can find out if you have a support plan. You should use the same subscription the storage account belongs to.

If you email me at AzCommunity, your email address doesn't matter to me.

Below is how you get the Azure subscription ID.

Below is how to find out if you have a support plan:

Share via

ADL Gen2 rename using Path REST API failure with SAS token