Azuredatastudio: Azure > Sign in to Azure.. > Add Account - [Not Working]

Created on 14 Feb 2020  路  9Comments  路  Source: microsoft/azuredatastudio



  • Azure Data Studio Version:

Steps to Reproduce:

  1. Click on Azure > Sign in to Azure.. > Add Account
    image

  2. Gets redirected to Local host with below Error
    image

Version Info:

Version: 1.15.0 (user setup)
Commit: e57eb999fc5f1e000477da8fe0b8679ff0bfd57b
Date: 2020-02-12T20:48:43.389Z
VS Code: 1.42.0
Electron: 6.1.6
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.18363

Area - Azure Bug Done

Most helpful comment

You can also see if you have HSTS enabled on localhost here:

(Assuming you're using chrome):

chrome://net-internals/#hsts

Query: localhost

It should look like this:

image

@aaomidi - Thanks for responding

  1. I do local dev. regularly , also see the screenshot below from my chrome
    image
  2. If copy paste the broken localhost url into another browser window and use http:// it works..

All 9 comments

Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

I got exactly the same problem with the same version info.

@aaomidi Can you look into this?

Moving into February Recovery milestone for hotfix consideration

@Git-BT-Hub thanks for reporting this issue! We have updated the auth mechanism in the Feb release to no longer use Device Code mechanism. While we troubleshoot this issue could you please try to reenable the Device Code mechanism to see if that helps mitigate the issue. You can enable the previous auth mechanism with the below setting.

Screen Shot 2020-02-14 at 10 14 52 AM

@Git-BT-Hub @jjusiak

Do you by any chance have an extension that is forcing https on localhost?

That error means you're trying to load localhost with https - which shouldn't happen.

Do you regularly do local development on localhost with https enabled? I can see the browser using a previous "upgrade" to https to think this website should also be https.

A way to mitigate this is:

  1. Let your browser load the broken page.
  2. Copy the URL from the address bar.
  3. Paste it into another browser, remove the https:// and change it to http://.
  4. Load that page.

I'll look into seeing if we can create alternative login mechanisms for when users are in this situation.

You can also see if you have HSTS enabled on localhost here:

(Assuming you're using chrome):

chrome://net-internals/#hsts

Query: localhost

It should look like this:

image

You can also see if you have HSTS enabled on localhost here:

(Assuming you're using chrome):

chrome://net-internals/#hsts

Query: localhost

It should look like this:

image

@aaomidi - Thanks for responding

  1. I do local dev. regularly , also see the screenshot below from my chrome
    image
  2. If copy paste the broken localhost url into another browser window and use http:// it works..

I've added the knowledge label to this because it contains information that would be interesting to reference in the future. However since this is a local environment problem, I'm going to close this issue.

The next release will also include device code login for people who have problems using the regular code grant method.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

kburtram picture kburtram  路  3Comments

sandermvanvliet picture sandermvanvliet  路  3Comments

blackTay picture blackTay  路  3Comments

Ungerfall picture Ungerfall  路  3Comments

Ungerfall picture Ungerfall  路  3Comments