Unable to login to production instance: Your authorization token has expired
We discovered this morning that we are unable to login to our production instance - cannot state how long this problem already exists exactly. When providing correct username and password, the UI will redirect and throw an "Your authorization token has expired" error in a modal popup. Only thing that is possible in this situation is to click "Login" which will then redirect on another page which then will redirect again. This redirect loop will again result in the same error popup. We already tried removing all cookies/local storage from the browser, tried all other browsers.
Is this a known ongoing issue? We havent changed anything on the instance in the last weeks? We are running on cloud version v4.6.1.
Cheers,
Stephan
9 Replies
Hi @stephanb, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.
Answer
Based on the available sources, there is a documented issue similar to what you're experiencing (1) . A GitHub issue describes a "Login V2 loop after user with active session is deactivated" where users get stuck in an automatic loop with the "Your authorization token has expired" message .
The issue describes that after a user is deactivated, user sessions remain valid, and Login V2 attempts to use the saved session when redirected to the login page . The user has no way to logout and ends up in a loop . The expected behavior is that after a user is deactivated, all sessions should be terminated .
Another similar case was reported where a user experienced constant reloading with a "Token Has Expired" notification after login (2) . In that instance, the issue resolved itself the next day when the server was restarted . One community member suggested this might be due to system clock being off by too much, and waiting/rebooting could solve the issue as an automated time sync could be triggered .
Since you're experiencing this on ZITADEL Cloud v4.6.1 and haven't made recent changes, I recommend clicking the "Ask for help" button to tag a team member who can investigate whether there's an ongoing issue with your specific instance or if user sessions need to be terminated.
To learn more, see the sources I considered:
[1] [Bug]: Login V2 loop after user with active session is deactivated
[2] Error: Login into Zitadel
Feel free to tag @Ask Inkeep with additional questions.
I have the same isue
Got it. Tagging @Rajat for additional help.
Unfortunately, the problem still persists and effects our production backend management capabilities tremendously. Any insights on this?
The same for me. But for some reason it affects only specific users.
hey @bkolasa @stephanb this has been identified internally and being worked on. I still dont have more updates atm but you can remove the MFA policy from the affected org if that helps for now. Thanks
Thanks for the update @Rajat . Currently this is not a viable workaround. We cannot change anything from the settings page that we currently have access to.
BTW The same happend for us.
We enabled force mfa for all users, this forces all users to activate mfa and than they can login. But just works if someone have mfa activated.
hey @Markus this issue has been worked on today and a fix a fix should be out either today/tomorrow.
Thanks