az login doens't redirect properly
See original GitHub issuewhen i use az login with the browser login, the redirect doesn’t redirect properly after signing in with my device and credentials (2 factor authentication).
I get “The page isn’t redirecting properly” error.
This is the url:
https://login.microsoftonline.com/common/oauth2/deviceauth?code=&state=<state>&flowtoken=<token>
If i try to login using user name and password, i get an error: Get Token request returned http error: 400 and server response: {“error”:“interaction_required”,“error_description”:“AADSTS50079: The user is required to u se multi-factor authentication.\r\nTrace ID: 393963bb-3961-4968-9517-a516c5c50100\r\nCorrelation ID: 448fe095-499f-43e9-9cb1-802f98ae0df1\r\nTimestamp: 201 7-11-17 20:34:54Z”,“error_codes”:[50079],“timestamp”:“2017-11-17 20:34:54Z”,“trace_id”:“393963bb-3961-4968-9517-a516c5c50100”,“correlation_id”:“448fe095-49 9f-43e9-9cb1-802f98ae0df1”}
Environment summary
PS C:\Users\user> az --version azure-cli (2.0.21)
acr (2.0.15) acs (2.0.19) appservice (0.1.20) backup (1.0.3) batch (3.1.7) batchai (0.1.3) billing (0.1.6) cdn (0.0.10) cloud (2.0.10) cognitiveservices (0.1.9) command-modules-nspkg (2.0.1) component (2.0.8) configure (2.0.12) consumption (0.1.6) container (0.1.13) core (2.0.21) cosmosdb (0.1.15) dla (0.0.15) dls (0.0.18) eventgrid (0.1.5) extension (0.0.6) feedback (2.0.6) find (0.2.7) interactive (0.3.11) iot (0.1.14) keyvault (2.0.14) lab (0.0.13) monitor (0.0.12) network (2.0.18) nspkg (3.0.1) profile (2.0.15) rdbms (0.0.9) redis (0.2.10) reservations (0.1.0) resource (2.0.18) role (2.0.14) servicefabric (0.0.6) sql (2.0.15) storage (2.0.19) vm (2.0.18)
Python location ‘C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe’ Extensions directory ‘C:\Users\user.azure\cliextensions’
Python (Windows) 3.6.1 (v3.6.1:69c0db5, Mar 21 2017, 17:54:52) [MSC v.1900 32 bit (Intel)]
Legal docs and information: aka.ms/AzureCliLegal)
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (4 by maintainers)
Top GitHub Comments
The MSFT employees who are a part of the inner ring by default need to opt out of the inner ring:
It is bad that the bug has been known for months and MSFT doesn’t seem to do much to fix it. Good luck!
Closing as the root cause is internal