Standard login failed but LDAP login working

Problem to solve

We have an on-premise installation of Gitlab CE.
We started configuring users directly in Gitlab and later we added LDAP (FreeIPA).
Our login page show both the LDAP and the standard authentication options.
I have always been able to use either to log in, but suddenly (after latest update maybe?) I am not able to login with my standard user and I have to use the LDAP user.

Steps to reproduce

The error simply states “Invalid login or password.”
I tried to find more detailed error messages in the logs, but was unable to.



System information
Current User: git
Using RVM: no
Ruby Version: 3.1.4p223
Gem Version: 3.5.5
Bundler Version:2.5.5
Rake Version: 13.0.6
Redis Version: 7.0.15
Sidekiq Version:7.1.6
Go Version: unknown

GitLab information
Version: 16.9.1
Revision: 0ef8ba69a8f
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: PostgreSQL
DB Version: 13.13
URL: https://git.domain_amended
HTTP Clone URL: https://git.domain_amended/some-group/some-project.git
SSH Clone URL: git@git.domain_amended:some-group/some-project.git
Using LDAP: yes
Using Omniauth: yes
Omniauth Providers:

GitLab Shell
Version: 14.33.0
Repository storages:

  • default: unix:/var/opt/gitlab/gitaly/gitaly.socket
    GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell


  • default Address: unix:/var/opt/gitlab/gitaly/gitaly.socket
  • default Version: 16.9.1
  • default Git Version: 2.43.0

+1 Same behavior in our self-managed docker GitLab CE after upgrading to 16.9.1

Users with standard login who never linked to LDAP are still able to use the standard login.

1 Like

I’m having the same issue on 16.9.2.

I have the same problem. Update to 16.10 has no effect