Login v2 - no console access
I'm trying out the v2 login in my self hosted instance, and I can successfully login, but I can no longer access the console. After logging in, if I try to navigate to the console, it logs me out and sends me back to the v2 login screen. What am I doing wrong here? The v2 login documentation needs a lot of work. Is there a v1 > v2 migration guide somewhere?
4 Replies
Hi @Dustin B, 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. Login users into your application with a hosted login UI : This contains information about Login v2 limitations and important notes about passkey/U2F authentication methods being bound to domains, which could affect console access when running on different domains (1) .
2. Route /ui/v2/login given in docs is not served by recent core version : This GitHub issue reports problems with the /ui/v2/login route not being served by recent core versions, indicating ongoing issues with v2 login implementation (2) .
To learn more, see the sources I considered:
[1] Login users into your application with a hosted login UI
[2] Route /ui/v2/login given in docs is not served by recent core version
Feel free to tag @Ask Inkeep with additional questions.
Got it. Tagging @Rajat for additional help.
nevermind, figured it out. My base URI was set as "/ui/v2" instead of "/ui/v2/login"
Glad I could be helpful. Feel free to create a new thread with any new questions you may have.
Also, in case anyone else stumbles upon this... https://zitadel.com/docs/self-hosting/deploy/compose has a section at the very bottom describing the steps to migrate an existing v1 login over to v2 (if using docker compose)