search

microsoft / AzureStorageExplorer

Easily manage the contents of your storage account with Azure Storage Explorer. Upload, download, and manage blobs, files, queues, tables, and Cosmos DB entities. Gain easy access to manage your virtual machine disks. Work with either Azure Resource Manager or classic storage accounts, plus manage and configure cross-origin resource sharing (CORS) rules.
Creative Commons Attribution 4.0 International
377 stars 87 forks source link

Sign-in Error: Only loopback redirect uri is supported, but urn:ietf:wg:oauth:2.0:oob was found #8247

Closed SSG11082 closed 3 weeks ago

SSG11082 commented 1 month ago

Below is the error I am facing when trying to sign-in to Azure Storage explorer. It was working fine earlier and started getting this error after a week of not logging in.

{ "message": "\"Only loopback redirect uri is supported, but urn:ietf:wg:oauth:2.0:oob was found. Configure http://localhost or http://localhost:port both during app registration and when you create the PublicClientApplication object. See https://aka.ms/msal-net-os-browser for details\"" }

MRayermannMSFT commented 1 month ago

@SSG11082

simonfox commented 1 month ago

I'm having the same problem after updating:

Image

Signing into Azure:

Image

SSG11082 commented 1 month ago

@SSG11082

  • What version of Storage Explorer are you using? 1.36.0
  • What Azure environment are you signing into? (Azure, Azure China, etc.) Azure
  • What sign-in method do you have selected in settings? (Auth broker, default browser, integrated sign-in, etc.) - After I select Subscription and Azure, it redirects me to direct sign-in and then error. not giving any option to choose sign in method
  • Can you try doing "Help" -> "Reset" -> choose only authentication -> select reset/ok -> restart Storage Explorer and try signing in again : Tried it and did not work. Still facing the same error.

Hello

Image

@MRayermannMSFT

JasonYeMSFT commented 3 weeks ago

If you are still able to reproduce the issue, could you please do us a favor to turn on the verbose logging, collect the authentication logs and share the logs with us? The logs may help us locate the cause of the issue and make a fix.

There are detailed instructions in this section of our troubleshooting guide https://learn.microsoft.com/en-us/troubleshoot/azure/azure-storage/blobs/alerts/storage-explorer-troubleshooting?tabs=Windows#authentication-logs

JasonYeMSFT commented 3 weeks ago

While we are investigating the issue, could you try changing the sign-in method to "default browser" and see if allows you to work around the issue as suggested by comments in this issue https://github.com/microsoft/AzureStorageExplorer/issues/8237? It would be very appreciated if you can reproduce the issue one more time and share the log with us.

craxal commented 3 weeks ago

Due to how widespread this issue is, we will be releasing 1.36.2 very soon to revert the default authentication method for Windows users.

For anyone having this issue, we invite you to do the following:

Help us diagnose

  1. Install Storage Explorer 1.36.x.
  2. Ensure you are signed out and that the "Sign in with:" setting is set to "Authentication Broker".
  3. Follow the troubleshooting docs to gather authentication logs.
  4. Please clear out any existing logs from the logs folder if you can.
  5. Share your logs by posting a comment in #8237!

Unblock yourself

  1. Install Storage Explorer 1.36.x.
  2. Change the value for the "Sign In with:" setting to be "Default Web Browser".
  3. Try signing in.

Thank you everyone for your patience and your help in diagnosing this issue!