Regressions in v2 login UI worry me - path forward?
š¬Self-hostedāQuestionāUnsolved
Hi! I've stumbled across this issue, which I have in my Zitadel deployment at the moment: https://github.com/zitadel/zitadel/issues/12434.
This is about a regression, where a persistent session across browser instances doesn't work anymore. In my view this is a pretty basic function for an IdP. This issue also has multiple effects like the OTP/2FA timeouts in the settings UI not working anymore (because there is no persistent session with v2 login). Now, in v3 of Zitadel the v2 login was still disabled by default. But in v4 this is enabled by default now.
Scrolling across GitHub issues at the moment and looking through the chat channels in this Discord, I see many issues regarding login v2, a lot of regressions (worked in v1, doesn't in v2) etc. Some things are disclaimed in the limitations section at https://zitadel.com/docs/guides/integrate/login/hosted-login#limitations but most are not.
It seems a bit premature to enable login v2 per default if a lot of ui features are not working, there are no persistent sessions, otp/2fa settings don't work anymore, text translations don't work anymore etc.
A comment on #12434 asked what the expected path forward is. Will all of these features be implemented in login v2 before login v1 get's removed? Will login v1 always be enabled as a full-featured fallback? What's the plan here?
This is about a regression, where a persistent session across browser instances doesn't work anymore. In my view this is a pretty basic function for an IdP. This issue also has multiple effects like the OTP/2FA timeouts in the settings UI not working anymore (because there is no persistent session with v2 login). Now, in v3 of Zitadel the v2 login was still disabled by default. But in v4 this is enabled by default now.
Scrolling across GitHub issues at the moment and looking through the chat channels in this Discord, I see many issues regarding login v2, a lot of regressions (worked in v1, doesn't in v2) etc. Some things are disclaimed in the limitations section at https://zitadel.com/docs/guides/integrate/login/hosted-login#limitations but most are not.
It seems a bit premature to enable login v2 per default if a lot of ui features are not working, there are no persistent sessions, otp/2fa settings don't work anymore, text translations don't work anymore etc.
A comment on #12434 asked what the expected path forward is. Will all of these features be implemented in login v2 before login v1 get's removed? Will login v1 always be enabled as a full-featured fallback? What's the plan here?
