← Directory

zitadel-login

ZITADEL v4 Login UI — the interactive sign-in pages (username/password, MFA, WebAuthn, etc.) for a ZITADEL v4 core instance.

  • Network Services
  • Security
ZITADEL v4 Login UI — the interactive sign-in pages (username/password, MFA, WebAuthn, etc.) for a ZITADEL v4 core instance. Since v4, ZITADEL split its interactive login pages out of the main API container into this separate service. Without it, every login attempt against a v4 "zitadel" container fails with a 404 on /ui/v2/login/login — this template exists to fix exactly that. REQUIRES the companion "zitadel" template from the same repository to already be running, using the exact same Bootstrap Volume path, since this container reads the login-client.pat token that ZITADEL writes there on its first start. Your reverse proxy needs a path-based rule so that requests to "/" and "/ui/v2/login/*" reach this container's port 3000, while everything else keeps going to the "zitadel" container's port 8080. See the setup guide below for an Nginx Proxy Manager example. Full setup guide:

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score

Not enough data yet for a health score. It needs at least 2 of 4 factors: maintenance, popularity, ease of install, resource needs.

Availability: platform listings confirmed today

No GitHub repository data collected yet.

Resources & Compatibility

Requirements not published yet.

Checked today - source: Docker Hub image tags and published docs

First-install notes

No first-install notes yet.

Alternatives (8)

  • Auth0 - You can connect any application (written in any language or on any stack) to Auth0 and define its Connection, the method used to authentica…
  • Authelia - Authelia is an open-source authentication and authorization server that provides login, multi-factor authentication, and single sign-on for…
  • Keycloak - Keycloak is an open-source Identity and Access Management platform for adding authentication to self-hosted applications.
  • Tinyauth - Tinyauth is a lightweight OpenID Connect authentication and authorization server that adds login and access controls to self-hosted apps be…
  • ZITADEL - Zitadel is an open-source identity and access management platform for self-hosted services, teams, and customers.
  • authentik - Authentik is an open-source identity provider that adds flexible single sign-on, user management, and common sign-in protocol support to se…
  • openam - OpenAM is an open-source access management platform providing authentication, single sign-on (SSO), and authorisation so users log in once…
  • rauthy - Rauthy is a lightweight and easy to use OpenID Connect Identity Provider.

Common questions

Why does a ZITADEL v4 login request to /ui/v2/login/login return 404?

The interactive login pages are no longer served by the main ZITADEL container, so the separate zitadel-login service must be deployed to serve the login UI.

How should the reverse proxy route ZITADEL v4 login traffic?

Route / and /ui/v2/login/* to zitadel-login on port 3000, and send all other paths to the main zitadel container.

What bootstrap volume configuration must match between zitadel-login and zitadel?

They must use the exact same Bootstrap Volume path because zitadel-login reads the login-client.pat token that ZITADEL writes there on first start.

Does zitadel-login provide the interactive MFA and WebAuthn steps?

Yes, it serves the sign-in pages for username/password, MFA, and WebAuthn flows.

Answers sourced from github.com, help.zitadel.com

Community

No community discussions collected yet.