Login policy corrupting without any logs, bug? (V2.14.)
Hi Everyone,
Self hosted zitadel instance on docker's login policy changes automatically without any logs for this change, could it be a bug or there are other ways that could impact the policy without being detected by the logs.
Thanks
5 Replies
Hey @SonalShekharš did you tried changing any login policies?
What did you exactlyy changed?
I didn't trigger any changes for login policy. I was just doing login, getting a user profile etc, no changes to settings were shown in logs as well. It was indeed changed on its own, the issue at login showed 'Errors.Org.IdpNotExisting (LOGIN-5Hm8s)'.
I know that this error comes when login policy is mis-configured for an org.
hey @SonalShekharš you can reset the login policy for now https://zitadel.com/docs/apis/resources/mgmt/management-service-reset-login-policy-to-default if you did nothing it should have not happened, did you tried upgrading your zitadel version tho, we already have
v3.x and v4.x https://zitadel.com/docs/product/roadmapHey @Rajat I have reseted the zitadel already, was trying to know if there is some known bug that could have caused this issue. I will try the upgrades, thanks.
There's no login policy related bug that we saw but if it kept repeating, feel free to open a bug ticket, chances are it should bw squashed if you run a newer Zitadel image