after LDAP login, the standard user login prompts an Invalid login or password.
Summary
After LDAP login, the standard user login prompts an Invalid login or password..
Steps to reproduce
Gitlab docker v16.11.1
- Create a standard user A with the email A@xx.com and set a password.
- Successfully login using the standard user account.
- Successfully login using LDAP (with the same email A@xx.com).
- Attempt to successfully login using the standard user account -- prompted with an invalid username or password.
- The administrator removes the LDAP login Provider for user A.
- Successfully login using the standard user account.
Example Project
What is the current bug behavior?
After a standard user logs in using LDAP, they are unable to log in again.
What is the expected correct behavior?
Both standard users and LDAP users can log in.
Relevant logs and/or screenshots
Output of checks
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`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
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
Edited by Dawn