microsoft
Unable to sign in via Default Web Browser and Integrated Sign-in
Preflight Checklist
- [X] I have installed the latest version of Storage Explorer.
- [X] I have checked existing resources, including the troubleshooting guide and the release notes.
- [X] I have searched for similar issues.
Storage Explorer Version
1.34.0
Regression From
No response
Architecture
x64
Storage Explorer Build Number
No response
Platform
Windows
OS Version
Windows 11
Bug Description
Unable to sign in to Storage Explorer via Default Web Browser and Integrated Sign-in 1- The Storage Explorer does not open a webpage for me to sign in when the Default Web Browser option is enabled. I also followed the troubleshooting guide of opening my web browser beforehand, but nothing happened.
2- I also tried the Integrated Sign-in option but nothing's happening expect that it's stuck with "Waiting for authentication"
3- I also tried to attach a Storage account using connection string but it's stuck with "Adding new connection..."
I haven't been able to install .NET 8 because I do not have admin rights. Does this affect the authentication?
Steps to Reproduce
- Launch Storage explorer
- Select Subscription and Sign in with Azure
Actual Experience
Nothing happens when I try to sign in via the following:
1- Default Web Browser - browser does not open
2- Integrate sign-in
3- Attach storage account
Expected Experience
No response
Additional Context
I haven't been able to install .NET 8 because I do not have admin rights. Does this affect the authentication?
Similar behavior here since the upgrade. Can't even tell you which version I'm on now, cause the UI is pretty broken and only shows empty stuff. Non of the 3 sign in options do anything. Logs were also not helpful. Completely blocked at work because of this now.
Hi @martinitus , Issue is now resolved on my end after installing .NET 8.
I was informed that Storage Explorer should still work without .NET 8 but it was the answer to my problem.
@inaaa-iio I believe that information may be out-of-date. If you look at our 1.34.0 release notes, you'll see that .NET 8 is now required.
Well, if dotnet 8 is required that explains it. i updated storage manager via the UI, but i don't have admin rights on the machine, so the dotnet8 update didn't go through. Quite pointless to allow updating the app into a broken state then :-/