Fail to rename the blob when entering a name contains " ' "

[v-xinda]

Storage Explorer Version: 1.15.0-dev
Build: 20200806.6
Branch: master
Platform/OS: Windows 10/ Linux Ubuntu 18.04/ MacOS Catalina
Architecture: ia32/x64
Regression From: Not a regression

Steps to reproduce:

1. Expand one ADLS Gen2 storage account -> Blob Containers.
2. Create one blob container -> Upload one blob -> Right click the blob -> Select 'Rename...' -> Enter "test'1".
3. Check the result.

Expect Experience:
Succeed to rename the blob.

Actual Experience:
Fail to rename the blob when entering a name "test'1".

More Info:
This issue doesn't reproduce on File Shares and regular Blob Containers.

[MRayermannMSFT]

@v-xinda can you still repro this? We're having a hard time doing so. Also, can you share with us the error details?

[v-xinda]

Hi @MRayermannMSFT
This issue also reproduces on the build 20200811.2. Error details as below.
Error Details:

{
 "name": "Error",
  "message": "This request is not authorized to perform this operation using this permission.\nRequestId:16f44a82-701f-00ab-6683-6fe84a000000\nTime:2020-08-11T02:04:13.4702143Z",
  "stack": "Error: This request is not authorized to perform this operation using this permission.\nRequestId:16f44a82-701f-00ab-6683-6fe84a000000\nTime:2020-08-11T02:04:13.4702143Z\n    at new RestError (C:\\Program Files (x86)\\Microsoft Azure Storage Explorer\\resources\\app\\node_modules\\@azure\\ms-rest-js\\dist\\msRest.node.js:2400:28)\n    at C:\\Program Files (x86)\\Microsoft Azure Storage Explorer\\resources\\app\\node_modules\\@azure\\ms-rest-js\\dist\\msRest.node.js:3544:37\n    at processTicksAndRejections (internal/process/task_queues.js:93:5)",
  "code": "AuthorizationPermissionMismatch",
  "statusCode": 403
}

[JasonYeMSFT]

@v-xinda The error message says the failure is due to missing permission. For rename (move) in ADLS Gen2, you will see such error details if you miss the "write" permission on the directory you are moving you blob into.

However, this doesn't seem to be the case. According to the issue description, you can upload a blob into the directory, meaning that you have "write" permission on that directory. Could you please make sure you try this with the write permission and see if the issue still reproduces?

[v-xinda]

@JasonYeMSFT Hi
Verified this issue on build master/20200818.4. Still reproduces.
More details please see the record: https://msit.microsoftstream.com/video/5517a1ff-0400-8385-52b4-f1eae0fd4a23

[JasonYeMSFT]

I still cannot reproduce the issue. Renaming a blob with name containing single quote ' just works fine.

[v-xianya]

@JasonYeMSFT

Verified this issue on build 20201010.6 and 1.15.1 release. Reproduce.

[JasonYeMSFT]

I managed to reproduce this issue. It only occurs when we use account name and key to authorize the rename action.

[MRayermannMSFT]

Jason, please open an issue against the SDK, and then move this to 1.18.

[JasonYeMSFT]

The issue is in the preview SDK and won't get fixed there. We need to upgrade to the public SDK to fix this issue.

[JasonYeMSFT]

A blocking issues in the public SDK has been fixed here Azure/azure-sdk-for-js#11849.

[JasonYeMSFT]

I just verified it today and it seems to have been fixed by integrating the new SDK.

[sid5233]

I'm still facing this issue. If I add my public IP address only then I'm able to rename the blob.

[JasonYeMSFT]

@sid5233 Could you open a new issue describing what you see? The original issue doesn't have anything to do with IP address. If you have a firewall setting, you are expected to add your IP in the rules.