question

KitLemmonds-4905 avatar image
0 Votes"
KitLemmonds-4905 asked Cathyji-msft commented

SSMS bug: stuck SAS token with Azure blob storage

I'm not sure where to report SSMS bugs anymore - or check to see if it's a preexisting bug, but I've just found one that cost me several hours: when generating a SAS token from SSMS's object explorer to restore from a backup on blob storage, SSMS does not prompt you to overwrite a pre-existing expired token. As a result, the "generated" token is not saved as a credential and the restore fails with "Access denied" because it still tries to use the "stuck" expired one. The only way to get SSMS to actually use the new token is to manually drop the old one first by running the following sql:

 DROP CREDENTIAL [https://<credential name>]

where <credential name> is typically the URL to the blob storage container, and can be found by running

 SELECT name from sys.credentials

Once the stuck token is manually dropped, the user can then go create a new one through object explorer and the restore will finally succeed.

Instead of generating an unusable SAS token, I believe SSMS should check for a preexisting credential to that resource and prompt the user to overwrite it ("A credential for that resource already exists. Would you like to replace it with this one?"). If the user selects "Yes," SSMS first executes the DROP CREDENTIAL and adds the new one.

sql-server-generalazure-blob-storage
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Cathyji-msft avatar image
0 Votes"
Cathyji-msft answered

Hi @KitLemmonds-4905,

I'm not sure where to report SSMS bugs anymore

Quote from MS user voice(MS feedback link);

We are evaluating enhancements and standardizations to improve and streamline how we communicate with customers and collect their feedback.

You can get assistance with your issue from different ways, suggest you reading MS document SQL Server help and feedback.


If the response is helpful, please click "Accept Answer" and upvote it, as this could help other community members looking for similar thread.



5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

KitLemmonds-4905 avatar image
0 Votes"
KitLemmonds-4905 answered Cathyji-msft commented

Thanks, @Cathyji-msft for the links. I have accepted your answer even though it's not satisfying. I understand that Microsoft is evaluating merging all feedback channels into a single solution, but the logical roadmap for that transition is to choose\deploy that solution first and THEN start migrating the existing feedback channels. Closing the existing feedback channels before having their replacement makes no sense.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @KitLemmonds-4905 ,

Right now UserVoice(feedback.azure.com) has been decommissioned and its replacement will be online in mid-October 2021.

If you have any wish to make feedback requests about SQL Server in the meantime, please provide us all the information listed below and we are glad to submit it on behalf of you.

Title:
Technical Feedback(Describe the precise feedback. Please avoid entering PII(Personally Identifiable Information)):
Business Scenario and Desired Outcome:
Issue Impact:
Workaround details if there are any:

Please be sure to explain things as much as possible, thanks for your patience.

Best regards,
Cathy

0 Votes 0 ·