microsoft / microsoft/AzureStorageExplorer

Allow updating SAS token for an existing SAS Blob Container connection

Open
#6,107 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
452
Forks
92
Avg merge
15h 20m
Merged PRs (30d)
3

Description

Preflight Checklist
Problem

Our team uses short-lived SAS tokens to access our data. When the week is up, we need to delete the existing container in ASE, and create a new one with the new SAS token. Any open tabs with their paths have to be closed and reopened with the new connection

Desired Solution

I'd like to be able to paste in a new SAS token for an existing connection, so all my tabs would continue to work. Or a button to edit the connection's properties.

Alternatives and Workarounds

We can work around this by closing and deleting everything associated with the old connection, but that requires re-navigating to each of the blob locations

Additional Context

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how Azure Storage Explorer creates and stores SAS Blob Container connections, then inspect how open tabs resolve their existing connection. Done means a user can replace the SAS token for an existing connection without deleting it or reopening tabs, with the updated connection continuing to access the container.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.