LDAP keeps requesting with old password

We are using LDAP authentication, and it has been working great for 1.5 years. Pr. security we change passwords every 3 months. Yesterday i changed mine, and all of a sudden my AD accont is locked. It turns out that gitlab is contionusly sending requests to the LDAP server using a wrong password. I can log into gitlab, pr. usual, and it will validate via. the LDAP server using the username/password provided in the login for, but gitlab will also request the LDAP server continously with a password that does not match my current profile. This then locks my AD account, like every 2 minutes... This does not happen to other employees that are using our gitlab server via LDAP.

The question is.

1. Why is gitlab continously requesting the LDAP server with my credentials (using a faulty password, could have been from a wrong input in the login form), even thou i am not actively logging into the gitlabserver.
2. Can i do something to stop this behaviour, besides disabeling LDAP, which is not feasible.
3. Would it help to delete/remove my current user in Gitlab?

I really need to get this fixed. Right now i have had to revert my LDAP password to the one the Gitlab is wrongly using behind the scenes just to be able to work.

System: Centos 7

GitLab 8.1.2

GitLab Shell 2.6.5

GitLab API v3

Ruby 2.1.7p400

Rails 4.1.12

Below is a trace of one of the LDAP request

Added ldap label

Is there any update on this? I have the same issue, however even changing to the old password doesn't fix it. Gitlab keeps trying to connect and fails and AD account locked out.

moved to gitlab#3899

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue

mentioned in merge request !14785