2 out of 5 GIT login fails with invalid_credentials encountered
Summary
We are using Git lab CE (8.14.4) from past one year but recently users started facing issues in GIT authentication with LDAP.
2 Out of 5 login attempt fails
Steps to reproduce
Login via CLI or UI
Example Project
Not applicable - Hosted in-house
What is the current bug behavior?
Login via CLI or UI - 2 out 5 login attempts fails
What is the expected correct behavior?
All login attempt should pass
Relevant logs and/or screenshots
unicorn_stdout.log
I, [2018-04-03T14:03:27.375391 #31066] INFO -- omniauth: (ldapmain) Callback phase initiated.
E, [2018-04-03T14:03:29.954372 #31066] ERROR -- omniauth: (ldapmain) Authentication failure! invalid_credentials encountered.
I, [2018-04-03T14:03:42.683145 #15096] INFO -- omniauth: (ldapmain) Callback phase initiated.
production.log
Parameters: {"utf8"=>"✓", "authenticity_token"=>"fh9Dphj73eWf2jJk3Fq/Mk0AGulssTrJYw3ebZ2mMEpZus8t5xkB2Lahaq7PrD5W+k+E13MlrRvmvxqGaDMHdA==", "username"=>"abc", "password"=>"[FILTERED]"}
Redirected to https://XXXXX/users/sign_in
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info
) gitlab-rake gitlab:env:infoSystem information
- System: CentOS 6.5
- Current User: git
- Using RVM: no
- Ruby Version: 2.3.1p112
- Gem Version: 2.6.6
- Bundler Version:1.13.6
- Rake Version: 10.5.0
- Sidekiq Version:4.2.1
GitLab information
- Version: 8.14.4
- Revision: 3ea6c8d7
- Directory: /opt/gitlab/embedded/service/gitlab-rails
- DB Adapter: postgresql
- URL: https://XXXXXX
- HTTP Clone URL: https://XXXXXX/some-group/some-project.git
- SSH Clone URL: git@XXXXXX:some-group/some-project.git
- Using LDAP: yes
- Using Omniauth: no
GitLab Shell
- Version: 4.0.3
- Repository storage paths:
-
- default: /data/gitlab/git-data/repositories
- Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks/
- Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
Not fixed. We tried to setup latest Git Lab CE 10.6.2 but behavior remains the same.