Use login v2 UI for both Zitadel console and application and customization
hi team, i am using latest Zitadel Helm Chart to deploy Zitadel (v4.4.0) i have two questions:
1. Any concerns of use the default zitadel-login UI for both Zitadel console and actual applications?
2. How to customize the text in V2 UI: https://github.com/zitadel/typescript/blob/main/locales/en.json
GitHub
typescript/locales/en.json at main · zitadel/typescript
Typescript packages and application to showcase the ZITADEL resource API - zitadel/typescript
3 Replies
Hi @kevinight, 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 about concerns with using the default Login V2 UI for both console and applications, or how to customize the Login V2 text strings. Here are some relevant sources:
1. Login users into your application with a hosted login UI (1) : Covers the hosted login page features and customization options including branding, but doesn't specifically address text customization for Login V2.
2. Set Instance Features (2) : Shows how to enable Login V2 at the instance level with the
loginV2 feature flag and optional baseUri configuration.
Would you like me to provide a general answer based on my knowledge instead?
**
To learn more, see the sources I considered:
[1] Login users into your application with a hosted login UI
[2] Set Instance Features
Feel free to tag @Ask Inkeep with additional questions.is it correct that Helm Chart, we are not able to customize the login v2 UI? @Ask Inkeep
if i self-host the UI, can it be a drop-in replacement for the zitadel-login by Helm Chart?
Thanks for the follow-up, @kevinight. I'll get back to you soon.
Answer
---
Regarding customizing the Login V2 UI with the Helm Chart: The documentation notes that "Custom Login Texts" is a current limitation of the Login V2 implementation (1) . However, you can customize branding aspects through ZITADEL's configuration .
For self-hosting the Login V2 UI as a replacement:
Yes, you can self-host the Login V2 UI and use it as a drop-in replacement (2) (1) . To connect your self-hosted Login UI to ZITADEL:
1. Create a machine user with a Personal Access Token (PAT) (2)
2. Ensure the user has the
IAM_LOGIN_CLIENT role
3. Configure your Login UI with the environment variable ZITADEL_SERVICE_USER_TOKEN set with your PAT, or mount the PAT file and reference it with ZITADEL_SERVICE_USER_TOKEN_FILE
For example, with Docker:
Then enable the Login V2 feature flag and enter the base URI of your Login UI (e.g., `http://localhost:3000/ui/v2/login%60) (2) (1) .
The self-hosted approach gives you full control to customize the login experience, including text strings, since it's built with Next.js and the source is available (1) .
To learn more, see the sources I considered:
[1] Login users into your application with a hosted login UI
[2] Connect your Self-Hosted Login UI to Zitadel | ZITADEL Docs
Feel free to tag @Ask Inkeep with additional questions.
Got it. Tagging @Rajat for additional help.