Failed to login by OpenLdap, the url userId is empty

Hi all,

I have set up Zitadel 4.7.0 using Docker Compose with PostgreSQL 17 as the database. I created a Netbird project and an organization, and configured OpenLDAP within the organization.

Currently, I'm encountering an issue: when logging in via LDAP, the following URL is generated:
https://auth2.xxx.xxx/ui/v2/login/idp/ldap/success?userId=&id=348233049676185603&token=oLEUiCWI7N_InR7qy3ziX5ViVaZeLMqme4lxE6p25caoAQ

The page returns a 404 error: "404 This page could not be found."

Here’s what I’ve confirmed:

The LDAP configuration is correct and functional. Evidence is shown below:```zitadel-# FROM eventstore.events2zitadel-# LIMIT 3;348233049676185603 | idpintent.ldap.succeeded | 2025-11-25 08:24:32.363037+00 | zhangqiang348233049676185603 | idpintent.started | 2025-11-25 08:24:32.257327+00 | ```
However, no user has been created and login hasn’t succeeded. I suspect a configuration issue, as shown below:```zitadel=# SELECT * FROM projections.idp_templates6 WHERE name = '9yb-ldap'; id | creation_date | change_date | sequence | resource_owner | instance_id | state | name | owner_type | type | owner_removed | is_creation_allowed | is_linking_allowed | is_auto_creation | is_auto_update | auto_linking 348232637711646723 | 2025-11-25 08:20:26.708175+00 | 2025-11-25 08:20:26.708175+00 | 84 | 346328751170191363 | 346328751170125827 | 1 | 9yb-ldap | 1 | 4 | f | t | t | t | t | 1(1 row)```

Actions I’ve already taken:

Consulted the official Zitadel AI support and raised multiple questions.
Sought help from other AI tools regarding this issue.

My troubleshooting has reached a dead end—there are no related events for

user.human.added

user.human.added

user.human.added

user.human.added.

Could anyone provide corresponding solutions?

Ask Inkeep•11/25/25, 8:57 AM

Hi @ccz, 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.

Ask Inkeep•11/25/25, 8:57 AM

Answer

I wasn't able to find a direct answer, here are some relevant sources:

Configure Local OpenLDAP as an Identity Provider in ZITADEL (1) : This guide covers the complete LDAP configuration process including required settings like Automatic creation and Automatic update flags that must be enabled for users to be created automatically within ZITADEL.
Set up Zitadel with Docker Compose (2) : This documentation covers Docker Compose setup including Login V2 configuration with environment variables like ZITADEL_DEFAULTINSTANCE_FEATURES_LOGINV2_REQUIREDZITADEL_DEFAULTINSTANCE_FEATURES_LOGINV2_REQUIRED and ZITADEL_DEFAULTINSTANCE_FEATURES_LOGINV2_BASEURIZITADEL_DEFAULTINSTANCE_FEATURES_LOGINV2_BASEURI.

Based on your database query showing is_auto_creation | tis_auto_creation | t and the idpintent.ldap.succeededidpintent.ldap.succeeded event, your LDAP authentication is working but the user creation step appears to be failing. The empty

userId

userId

parameter in your redirect URL suggests the user object wasn't created before the redirect.

Check your ZITADEL logs for any errors during the user creation process, and verify your Login V2 service is running and properly configured to handle the /ui/v2/login/idp/ldap/success/ui/v2/login/idp/ldap/success endpoint .

Ask Inkeep•11/25/25, 8:57 AM

To learn more, see the sources I considered:

[1] Configure Local OpenLDAP as an Identity Provider in ZITADEL
[2] Set up Zitadel with Docker Compose

Ask Inkeep•11/25/25, 8:57 AM

Feel free to tag @Ask Inkeep with additional questions.