You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Experiencing difficulties when generating a SAS (Shared Access Signature) assigned IP for a specific container in Microsoft Azure Storage Explorer.
#7580
Closed
3 tasks done
NicolasGomez97 opened this issue
Dec 13, 2023
· 4 comments
I am currently experiencing difficulties generating a SAS (Shared Access Signature) for a specific container in Microsoft Azure Storage Explorer.
Steps to Reproduce
Steps to reproduce the issue
I open Microsoft Azure Storage Explorer.
I generate a SAS for a specific container with the IP of my local machine.
I try to copy, move or rename a file or folder within that container.
I note that these actions are not allowed.
Actual Experience
However, when generating the SAS with the IP of my local machine, I run into limitations. I am unable to perform the functions mentioned above (copy, move, rename, etc.).
Expected Experience
When I generate a SAS with the IP of my local machine, I expect to be able to perform all the functionality available in the Microsoft Azure Storage Explorer, such as copy, move, rename, etc.
Additional Context
This problem does not occur when I generate a SAS without including the IP of my local machine.
Have there been any recent changes made to Azure Storage Explorer configuration or SAS generation that could be related to this issue?
The text was updated successfully, but these errors were encountered:
@NicolasGomez97 Has using an IP worked with previous versions of Storage Explorer? Have you verified that you're using the correct IP (for example, not using 127.0.0.1)?
@NicolasGomez97 If your device is behind NAT (not assigned a global IP), you may need to use methods like whatismyipaddress.com or a STUN server to get your Internet facing IP address.
@JasonYeMSFT It is not a NAT or firewall problem, because it allows me to do some functionalities. In any case, if that would be the problem, it would not let me do anything. But the bug comes when I want to do some of the following functionalities:
Rename
Move or copy files and folders
Delete files and folders
Features that it does let me do:
Upload Files and Folder
*Download Files and folder
*Create folder.
web my ip: https://www.myip.com/
Permissions:
@NicolasGomez97 For operations like copy, rename and move, the server needs to access the source. If your SAS token IP parameter restricts the server it won't be able to do so. However, delete should work. I tested in 1.32.1 and my delete worked.
Preflight Checklist
Storage Explorer Version
1.32.1
Regression From
No response
Architecture
x64
Storage Explorer Build Number
20231114.10
Platform
Windows
OS Version
Windows 10
Bug Description
I am currently experiencing difficulties generating a SAS (Shared Access Signature) for a specific container in Microsoft Azure Storage Explorer.
Steps to Reproduce
Steps to reproduce the issue
Actual Experience
However, when generating the SAS with the IP of my local machine, I run into limitations. I am unable to perform the functions mentioned above (copy, move, rename, etc.).
Expected Experience
When I generate a SAS with the IP of my local machine, I expect to be able to perform all the functionality available in the Microsoft Azure Storage Explorer, such as copy, move, rename, etc.
Additional Context
The text was updated successfully, but these errors were encountered: