This is a text-only version of the following page on https://raymii.org: --- Title : Gitlab Active Directory LDAP Authentication Author : Remy van Elst Date : 28-05-2013 URL : https://raymii.org/s/tutorials/Gitlab_and_Active_Directory_LDAP_Authentication.html Format : Markdown/HTML --- Gitlab is a self hosted git based source control application similar to Github, written in Ruby on Rails. It is used by many organisations and is a wonderfull piece of software. It supports LDAP Authentication (via the OmniAuth Gem), but it is tricky to set up with Active Directory and Windows Server 2003/2008/2012. This tutorials shows you how to set up Gitlab to authenticate against Active Directory LDAP.

Recently I removed all Google Ads from this site due to their invasive tracking, as well as Google Analytics. Please, if you found this content useful, consider a small donation using any of the options below:

I'm developing an open source monitoring app called Leaf Node Monitoring, for windows, linux & android. Go check it out!

Consider sponsoring me on Github. It means the world to me if you show your appreciation and you'll help pay the server costs.

You can also sponsor me by getting a Digital Ocean VPS. With this referral link you'll get $100 credit for 60 days.

You have to have a working Gitlab installation for this. It is tested with Gitlab 3 and up to 5.2, with an Active Directory 2008 env, and a Mixed 2008 & 2003 AD. Gitlab is installed on a Ubuntu box. First create a user in the Active Directory. My CN is Users, and my user is named `gitlab`. It does not have any special permissions, it is just a normal user. Note the Full Name you use, in my example it is "Gitlab LDAP". See the image below for an example: ![windows-gitlab][2] Now go to your Gitlab server, log in and become the git user: sudo su - git And edit the `~/gitlab/config/gitlab.yml` file. (Assuming you followed the official installation guide, otherwise adapt path.). The relevant LDAP section should contain this: ldap: enabled: true host: 'pdc1.domain.tld' base: 'CN=Users,DC=Domain,DC=tld' port: 389 uid: 'sAMAccountName' method: 'plain' # or "ssl" bind_dn: 'CN=Gitlab LDAP,CN=Users,DC=Domain,DC=tld' password: 'example_password' It took me a while to find the correct `bind_dn` and `base_dn`. It appears that they are capital sensitive, `cn=Users` would not work, but `CN=Users` does. Also, the `bind_dn` does not use the users email address, but the `Display Name`. So `CN=gitlab@domain.tld` does not work, but `CN=Gitlab LDAP` does. Hope this helps you setting up Gitlab with LDAP auth. More info on Gitlab can be found on their website: . [1]: https://www.digitalocean.com/?refcode=7435ae6b8212 [2]: https://raymii.org/s/inc/img/gitlab-1.png --- License: All the text on this website is free as in freedom unless stated otherwise. This means you can use it in any way you want, you can copy it, change it the way you like and republish it, as long as you release the (modified) content under the same license to give others the same freedoms you've got and place my name and a link to this site with the article as source. This site uses Google Analytics for statistics and Google Adwords for advertisements. You are tracked and Google knows everything about you. Use an adblocker like ublock-origin if you don't want it. All the code on this website is licensed under the GNU GPL v3 license unless already licensed under a license which does not allows this form of licensing or if another license is stated on that page / in that software: This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see . Just to be clear, the information on this website is for meant for educational purposes and you use it at your own risk. I do not take responsibility if you screw something up. Use common sense, do not 'rm -rf /' as root for example. If you have any questions then do not hesitate to contact me. See https://raymii.org/s/static/About.html for details.