Unable to connect via 2FA - "This site can't be reached"

[dvasdekis]

• MSSQL Extension Version: v1.15.0
• VSCode Version: 1.68.1
• OS Version: Windows 10 Enterprise 21H2

Steps to Reproduce:

1. ctrl+shift+p, create new connection, enter SQL Server details
2. Link is generated, like http://localhost:61997/signin?nonce=PnOsArasdasdasfk2fHhch%252BA%253D%253D
3. Go to link, but it says "This site can’t be reached. localhost refused to connect." Not sure how to debug further.

Unlike #17234, I don't get the chance to click an account name.

I don't have a choice but to use 2FA for Synapse SQL OnDemand servers, so I don't have an alternative at this time to this approach.

[Charles-Gagnon]

Are you able to use the device code auth method?

[Katzmann1983]

First step is always to completely delete your browser history. Some cached tokens there (especially when changing passwords) might screw over this extension.

[jan-hudec]

Are you able to use the device code auth method?

For me the DeviceCode works.

First step is always to completely delete your browser history. Some cached tokens there (especially when changing passwords) might screw over this extension.

Cached tokens, nor anything else in the browser local storage, did not get opportunity to screw anything yet, because the link the browser was given cannot be opened. Because the server in the extension appears not to be listening.

Besides, telling the user to just clear local data when problem occurs, especially all local data rather than local data for specific site, is rude. Some of the data in local storage are rather important and will cost significant time to recreate or restore later.

[cheenamalhotra]

Checking in, does anyone still experience this issue? We are hopeful this issue should be resolved, let us know if you're experiencing any Azure authentication issues.

[cheenamalhotra]

Closing as inactive issue