question

CasperPieterse-3696 avatar image
0 Votes"
CasperPieterse-3696 asked CasperPieterse-3696 commented

Azure Stack Edge Blob Storage - Server Failed To Authenticate

I'm following the directions as per https://docs.microsoft.com/en-us/azure/databox-online/azure-stack-edge-gpu-manage-storage-accounts

However, when trying to connect using the Azure Storage Explorer, I'm greeted with an error "Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature."

Using the same key against the public peer works fine.

Any ideas?

azure-blob-storageazure-stack-hub
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.

1 Answer

deherman-MSFT avatar image
0 Votes"
deherman-MSFT answered CasperPieterse-3696 commented

@CasperPieterse-3696

There is currently a known issue with Azure Storage Explorer which is likely causing this issue. They are currently working on a fix with plans to deploy in the next release. You can view and track the issue here.

Apologies for the issue. If you have further questions or issues please let us know.



Please don’t forget to "Accept the answer" and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

· 2
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.

Does this affect the SDK as well?

0 Votes 0 ·

The issue is not with Explorer or the SDK it seems. The edges are rejecting any client with a service version after 2019-07-07. I got around the issue when using the SDK by specifying a version through adding

 new SpecializedBlobClientOptions(BlobClientOptions.ServiceVersion.V2019_07_07) 

into the constructor of the blob client.

No idea if there is a way to specify a different version for explorer.

0 Votes 0 ·