Azurite does not support “Bearer Tokens”īut fear not, I have a solution for you. Token Issue: DefaultAzureCredential uses “Bearer Tokens”. Azurite and Storage Explorer do not support HTTPS. HTTPS Issue: DefaultAzureCredential requires HTTPS. So even if you run Azurite with HTTPS, you still need token support for DefaultAzureCredential, and Storage Explorer can’t talk to the HTTPS endpoints.
The current problem is that Azurite doesn’t support HTTP or Token based authentication, which the new Azure Identity DefaultAzureCredential requires, and Storage Explorer only supports HTTP.
Second, you love the new Azure Identity DefaultAzureCredential class and want to use it with your local emulation tools. You can emulate Azure Storage with Azurite and you can peek into your storage account with Storage Explorer. If you are like me, then first, you love to save money and not hit the cloud when you don’t have to use of local tooling and emulators is a great way achieve that. You won’t need to create a reverse-proxy anymore like I describe in this post below. Please see my new blog here for all the details. UPDATE - Azurite now officially supports HTTPS and OAuth.
0 kommentar(er)
