Active Directory account lockouts after git push
Hi, I am running GitLab 8.5.1 CE Omnibus on CentOS 6.7, though this issue has existed since we started using GL on 7.x.
I've had an issue where GitLab is causing my LDAP-enabled user account to become locked out in AD. Our Active Directory server will lock out a user if there are a) too many failed password attempts or b) are a "flood" of requests in a short period of time (rate limiting). I seem to be hitting b). And for some reason it seems more prevalent on a git push after I've merged in other developer's changes from the GitLab repo and pushed again, i.e. git pull, accept merge, git push.
Per What sort of queries can my LDAP server expect from GitLab EE?, I see that GitLab can make 1-2 LDAP requests per "interaction" with GitLab.
Questions:
- Is there any way to tell from the logs under /var/log/gitlab how many or what requests are being made to my LDAP/AD server? I've looked but do not see anything being logged at this time.
- Would a git push containing more than one commit equate to more LDAP queries, as opposed to a git push containing a single commit?
Any thoughts or help troubleshooting are appreciated.