You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Zitadel defaults to using an IdP if one was previously used by a user. When an auth request happens and Zitadel is aware of a linked IdP, the user is redirected silently without asking if other methods (like password) are preferred instead. Only when the IdP login flow fails, we present options as a fallback.
There are situations where this is not desired. As per incoming support case:
Our case for this is simple: at some clients onsite, we are not able to login via Microsoft due to their corporate network policies. In this case, the Idp gets stuck, without Zitadel detecting it (because the warning is on the Microsoft side).
The current flow is desired by many of our users / customers and therefore we can't change the behavior globally.
Preflight Checklist
Describe your problem
Currently Zitadel defaults to using an IdP if one was previously used by a user. When an auth request happens and Zitadel is aware of a linked IdP, the user is redirected silently without asking if other methods (like password) are preferred instead. Only when the IdP login flow fails, we present options as a fallback.
There are situations where this is not desired. As per incoming support case:
The current flow is desired by many of our users / customers and therefore we can't change the behavior globally.
Describe your ideal solution
Acceptance criteria
Version
No response
Environment
ZITADEL Cloud
Additional Context
After zitadel/zitadel#9318
The text was updated successfully, but these errors were encountered: