Gitlab block user for a mistake in ldap dn for case sensitive diferences

Hello every one
Im trying to conect gitlab with ldap to centralize my authentication.

Im having a problem when i try to log in because gitlab blocks the users.

The base_dn where the users are is ou=People,dc=dominio,dc=com
When i try to log in all works fine until Gitlab make a sync and block the user because on the gitlab database the base_dn is saved in lowcase.

LDAP account "uid=user1,ou=people,dc=dominio,dc=com" does not exist anymore, blocking GitLab user "Usuario" (

Gitlab is able to read all the info from the user in theLDAP and also create the user on the gitlab system(full name, email, etc).

User "Usuario" ( was created
But later block the user and im not able to log in, every time i unblock manually, the gitlab block again.

Here all the process:

User "Usuario" ( was created
(LDAP) saving user from login with admin => false, extern_uid => uid=user1,ou=people,dc=dominio,dc=com
LDAP account "uid=user1,ou=people,dc=dominio,dc=com" does not exist anymore, blocking GitLab user "Usuario" (

When i check in the user profile they show this info:
LDAP uid: uid=user1,ou=people,dc=dominio,dc=com

In the LDAP the real path is:

Some idea how i said to gitlab rescpect the upercase or not be case sensitive?

Have you found any solution to this? I don’t think it is related to case sensitivity because I am having this same problem trying to authenticate with LDAP. When I set uid=cn in the gitlab.rb config I am able to log in using accounts with their RDN set to cn or to uid by using their cn value as the username, but when I set uid=uid I get the behavior you describe here.

Yes i solve…
My issue was with the filters…

Gitlab dont suport multiple filters… i need to use a diferent aproach and works