Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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
Assignees
Labels
✅ by design Issue is intentional (not a bug)
Milestone

Comments

@NicolasGomez97
Copy link

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

  1. I open Microsoft Azure Storage Explorer.
  2. I generate a SAS for a specific container with the IP of my local machine.
  3. I try to copy, move or rename a file or folder within that container.
  4. 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.).

image

image

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.
    image

image

  • Have there been any recent changes made to Azure Storage Explorer configuration or SAS generation that could be related to this issue?
@craxal craxal added :accessibility: accessibility Related to keyboard accessibility and removed :accessibility: accessibility Related to keyboard accessibility labels Dec 13, 2023
@craxal
Copy link
Contributor

craxal commented Dec 13, 2023

@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)?

@JasonYeMSFT
Copy link
Contributor

@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.

@NicolasGomez97
Copy link
Author

@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/
    image
    Permissions:
    image

@JasonYeMSFT JasonYeMSFT added this to the 1.33.0 milestone Jan 22, 2024
@JasonYeMSFT JasonYeMSFT self-assigned this Jan 22, 2024
@JasonYeMSFT JasonYeMSFT added the ❔ investigate We need to look into this further label Jan 22, 2024
@JasonYeMSFT
Copy link
Contributor

@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.

@JasonYeMSFT JasonYeMSFT added ✅ by design Issue is intentional (not a bug) and removed ❔ investigate We need to look into this further labels Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✅ by design Issue is intentional (not a bug)
Projects
None yet
Development

No branches or pull requests

3 participants