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

Please allow key selection when getting shared access signature in blob container #1659

Closed
John-Garrett opened this issue Aug 13, 2019 · 1 comment
Assignees
Labels
💡 feature request New feature or request ✅ merged A fix for this issue has been merged
Milestone

Comments

@John-Garrett
Copy link

Is your feature request related to a problem? Please describe.
When using Azure Portal to get a shared access signature for a blob container, there's no way to select which access key is used to generate the secret. Key 1 is always used. Please allow key selection at this time.

Describe the solution you'd like
When you select your storage account, select storage explorer, expand blob containers, right click your blob container, select Get Shared Access Signature. In the next window where you select access policy, start and expiry time, and permissions, please add a dropdown for which key will be used to generate the secret used in the query string.

Describe alternatives you've considered
The only alternative, as far as I know, to specify the access key is with powershell, as shown here: https://docs.microsoft.com/en-us/sql/relational-databases/tutorial-use-azure-blob-storage-service-with-sql-server-2016?view=sql-server-2017

Additional context
This process would make it easier for quick one-offs where scripting the solution may be impractical, but you still want the flexibility of specifying key 2 instead of the default key 1.

@MRayermannMSFT MRayermannMSFT added the 💡 feature request New feature or request label Aug 19, 2019
@MRayermannMSFT MRayermannMSFT added this to the 1.13.0 milestone Aug 19, 2019
@MRayermannMSFT MRayermannMSFT modified the milestones: 1.13.0, 1.14.0 Mar 2, 2020
@MRayermannMSFT
Copy link
Member

Related to #421

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💡 feature request New feature or request ✅ merged A fix for this issue has been merged
Projects
None yet
Development

No branches or pull requests

4 participants