Forum Discussion
Blob SAS Token and Signature format
Hi,
I was planning to use private endpoint for my storage account, but when copying the file by AZCopy I'm getting only feedback:
"Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature."
I was looking for others and seems that incorrect formats seems quite common challenge but was not really able to find the valid solution. When running AZCopy from command prompt, some has replaces "&" with "&&" and so on.
Is there general rule how the SAS Token should look like when using that on command prompt? Also I tested this URL on my browser and that only returned:
<AuthenticationErrorDetail>Signature fields not well formed.</AuthenticationErrorDetail>
One question is also, should it be possible to test on browser only?
2 Replies
- Petri-XBronze Contributor
Hi Kidd_Ip
Thanks for your reply, but is it expected to get such an error if the connection is blocked by the firewall? But actually, before these tests I have verified by PortQry that I can reach the port 443 from my private end point.
But your question was of course valid 🙂 The FW is there and public connection is blocked, but private endpoint is approved.