[Bug] InteractiveBrowserCredential gets "This site can’t be reached" sometimes #5279
Labels
confidential-client
needs attention
Delete label after triage
untriaged
Do not delete. Needed for Automation
Library version used
Azure.Identity 1.13.2
.NET version
.net 9
Scenario
ConfidentialClient - web api (AcquireTokenOnBehalfOf)
Is this a new or an existing app?
The app is in production, I haven't upgraded MSAL, but started seeing this issue
Issue description and reproduction steps
Originally raised on the Azure board, raised here too on advice by @christothes
Some users report that when they are asked to login from the browser, that after picking their user, they get a "This site can't be reached". the URL appears to be a localhost address (in this instance localhost:49203/?code=[auth code response]) I theorise that the browser is booted up and displayed before a locally hosted web server to retreive the callback token is fully started up.
Relevant code snippets
Expected behavior
a login where a user is "quick" to respond to the login request, shouldn't cause an adverse experience.
Identity provider
Microsoft Entra ID (Work and School accounts and Personal Microsoft accounts)
Regression
No response
Solution and workarounds
Waiting for a while and refreshing the page works.
The text was updated successfully, but these errors were encountered: