AUTHZ-Kl3p0
I suddenly receive the following error when logging in as an instance administrator: mfa_required (AUTHZ-Kl3p0). I did not change anything in the configuration and this is our only administrator account that we can login with. Any clue why this happens and how i can regain access to the instance?
13 Replies
Hi @Arwin, 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
I wasn't able to find a direct answer, here are some relevant sources:
1. Breaking changes in minor versions (1) : This discusses a change in v3.4.3 where MFA enforcement behavior was modified - if a user has MFA set up, it's now required regardless of policy settings, which may explain the sudden MFA requirement.
2. How to regain access in a self hosted instance? (2) : This provides detailed steps for regaining access to a locked-out self-hosted instance by creating a System User with appropriate roles and using the API to unlock or modify users.
To learn more, see the sources I considered:
[1] Breaking changes in minor versions
[2] How to regain access in a self hosted instance?
Feel free to tag @Ask Inkeep with additional questions.
Got it. Tagging @Rajat for additional help.
This indeed seems like it is caused by the 1st source linked by inkeep above, but there seems to be no concrete answer or resolution for my situation yet
I too have this issue...
hey @Arwin @spicypixel this has been idenitified and a fix is on its way.
cc @elina_shoko
Oh good this is great news
Thanks @Rajat ! That is great news. Any idea about the timeline?
yeah it's affecting 20% of our users currently, given them a loose "one business day" timeline currently but got nothing here to work on
🥲
hey @spicypixel @Arwin good morning, Livio and the team are still fixing it as it has affected others users too. I will share more imformation when I have
Thanks
Can’t for regulatory reasons sadly
Any update?
Or a github issue/pull request I can subscribe to?
hey @spicypixel no not today I think, I raised this question internaly and no response yet
I for one will continue to keep telling the affected users good luck