-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
inability to login using my az cli: The ID token is not yet valid #20434
Comments
@jiasli for awareness |
Duplicate of #20158 Please check the solution at #20158 (comment) |
|
As the error suggested: Current epoch = 1635894218. This is 2021-11-2 23:03:38 UTC (converted using https://www.epochconverter.com/). This issue was raised at 2021-11-2 21:57 UTC. Make sure the local time of you machine is correctly set. |
I'm facing the same issue and local time is correctly set (epoch and my local time are same). Please explain what needs to be done to make az login work. |
@shelly-goel, could you share the detailed error message with the decoded ID token? |
$ az login |
Per https://www.epochconverter.com/, the current epoch time is |
the output I shared was from last execution sometime back. Current execution is below and close to current epoch time |
The time you posted this is |
Computer is configured with Internet time, not sure what you mean "synchronized to correct time". I executed again and command shows: Current epoch = 1637596031 whereas https://www.epochconverter.com shows: Current epoch = 1637596050 |
https://www.epochconverter.com/ shows |
I see what is going on. https://www.epochconverter.com/ is actually showing the local computer time! Could you try to adjust your computer's time according to https://time.is/ ? |
It works now, thanks! |
Detailed summary is provided in #20388 (comment). |
Why is #20388 put in backlog, by the way? All these issues should be closed as an FAQ, |
Azure CLI Tools team doesn't use Discussion for issue triage and management yet. Also, the issue linking feature of Discussion is very limited. That's why we want to keep using Issues. |
I'm hitting this problem even though https://time.is/ is showing my time as "exact" with the message "The difference from Time.is was -0.001 seconds (±0.067 seconds). " Please advise what steps should be taken. $ az login |
Did you run your "az login" on your local desktop, or on a remote VM? In the latter case, https://time.is won't be able to detect your remote VM's time. The error message contained:
Based on that error message, the machine running "az login" was 3 hours behind the AAD server's time. Can you still reproduce this issue? If so, you can use online tools such as https://www.epochconverter.com/ to convert those timestamps back to GMT or your local time. And see if that would give you/us more hint. |
For people who use WSL2 and Azure CLI, there is an active issue "WSL2 date incorrect after waking from sleep" for now You can verify if time matches with this command:
And this workaround works for me - |
Had the same issue on WSL2, which the clock was out of sync. Solved it by running |
It works for me to force time zone synchronization
|
This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az login
Errors:
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
az login
Expected Behavior
Environment Summary
Additional Context
The text was updated successfully, but these errors were encountered: