Support Custom Azurite Accounts/Unable to connect to custom azurite accounts: Server failed to authenticate the request. #4163
Comments
|
@GeeWee Did you select the SAS option or the account name and key option? Your connection string doesn't have a SAS, so I would expect the panel to invalidate that input. Can you examine the requests on the receiving end? Is Azurite in your Docker container getting the requests? |
|
Good question, I actually tried out both. I inspected the azurite logs. The requests do happen. I also tried the verbose error logs to see if anything good came out of it, but unfortunately it didn't really reveal any information. Perhaps the right call here is to still allow people to use connection strings? |
|
Since you're connecting to an emulator, we can look further into allowing connections to emulators using connection strings. This would likely add a selection panel where you can choose between connection strings or port numbers. |
|
Create #4177 to track connection string entry as well. |
|
We need to investigate if directly using connection string with a varied development account name works. |
|
We had a bug in the url construction code for such local endpoints with custom storage account names, so they don't work in 1.18.1. I made a fix for the url construction, which should allow connecting to Azurite with custom account names via connection strings. But this isn't obvious for emulator and we need to revisit our emulator connection experience. |
MRayermannMSFT
changed the title
|
We'll try to get to supporting this via the attach emulator experience, but for now, starting with Storage Explorer 1.19, you can attach a custom azurite account by constructing the connection string yourself. |
Storage Explorer Version: 1.18
Build Number: 20210227.4
Platform/OS: Fedora 33
Architecture: x64
Regression From: Yes, but unsure which one. I think before the new connection dialog.
Bug Description
I am unable to add custom Azurite storage accounts anymore.
I have the following azurite (in docker) configuration
(Note that none of these keys are secret, don't worry about that, they are only used locally)
Previously I would add these by connection string. Now I'll add them through Connect>Storage Account>SAS
and input e.g. the following signature
DefaultEndpointsProtocol=http;AccountName=stoperational001;AccountKey=Zm9v;BlobEndpoint=http://127.0.0.1:10000/stoperational001;QueueEndpoint=http://127.0.0.1:10001/stoperational001;When I try to list blobs or anything, I get the following error:
Note these following characteristics:
DefaultEndpointsProtocol=http;AccountName=devstoreaccount1;AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==;BlobEndpoint=http://127.0.0.1:10000/devstoreaccount1;QueueEndpoint=http://127.0.0.1:10001/devstoreaccount1;or through the built-in option for thatThe text was updated successfully, but these errors were encountered: