Login v1 vs Login v2 for production launch
Hello Zitadel Team and Community,
We have successfully integrated the self-hosted version of Zitadel into our SaaS solution and are now preparing for our production launch. As we finalize our setup, we're looking for some advice on whether to use Login V1 or V2, and we would be grateful for your guidance.
Our initial plan was to use the new Login V2, since it’s the recommended stable default in v4.0. However, we've found that our go-live is currently blocked by several important bugs such as Domain Discovery in #10662, UI customizations in #580, #581, #582, #583 (typescript repo) and SAML POST-Redirect in #10759. This creates a significant dilemma for us, especially when looking at the public roadmap. We've seen that Login V1 is planned to be deprecated in the next major iteration, V5, supposedly as early as November.
This leaves us with two choices, neither of which seems ideal:
- Go live with Login V1, which appears stable, but this would require a migration to V2 just a few months (or even weeks) after our launch.
- Wait to go live with Login V2, but this depends on critical bug fixes that don't have a clear timeline, which puts our own project schedule at risk.
Given this context, we would really appreciate a clear recommendation from the team:
- For a company in our position, about to go into production, what is the officially recommended path today? Should we use V1 and perhaps expect a delay in its deprecation, or should we wait for a stable patch for V2?
- Considering the current state of Login V2, is the November timeline for V5 (and the removal of Login V1) still realistic?
Any transparency on this would be immensely helpful for our planning and would strengthen our confidence in building our business on Zitadel. We'd also be very interested to hear if other community members are facing a similar dilemma and how they are approaching it.
Thank you for your amazing work on this project and for your support.
1 Reply
Hi @Helixo, 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. Zitadel Release Versions and Roadmap : The roadmap shows Login V2 moved to General Availability in v4.x and that Login V1 will be removed in v5.x, but doesn't provide specific timelines for v5 release.
2. Set up Zitadel with Docker Compose : Shows Login V2 is enabled by default in new installations with
ZITADEL_DEFAULTINSTANCE_FEATURES_LOGINV2_REQUIRED: true but you can disable it by setting this to false for Login V1.
For specific guidance on production deployment decisions and timeline concerns, I'd recommend clicking the "Ask for help" button to tag a team member for official recommendations.
Feel free to tag @Ask Inkeep with additional questions.
Got it. Tagging @Rajat for additional help.