Hi, I am using the gitlab omnibus package on Centos 6.5 and I *HAD* LDAP working with the following settings in "/etc/gitlab/gitlab.rb":
> # These settings are documented in more detail at > # > https://gitlab.com/gitlab-org/gitlab-ce/blob/master/config/gitlab.yml.example#L118 > gitlab_rails['ldap_enabled'] = true > gitlab_rails['ldap_host'] = '[My host removed]' > gitlab_rails['ldap_port'] = 389 > gitlab_rails['ldap_uid'] = 'sAMAccountName' > gitlab_rails['ldap_method'] = 'plain' # 'ssl' or 'plain' > gitlab_rails['ldap_bind_dn'] = 'CN=Gitlab LDAP,OU=Corporate,OU=[My OU > Removed],DC=[My DC removed],DC=com' > gitlab_rails['ldap_password'] = '[My passwd removed]' > gitlab_rails['ldap_allow_username_or_email_login'] = true > gitlab_rails['ldap_base'] = 'OU=Corporate,OU=[My OU Removed],DC=[My DC > removed],DC=com' I moved the bind user to the OU "Service Accounts" and now it is not working. I changed the pertinent line to: gitlab_rails['ldap_bind_dn'] = 'CN=Gitlab LDAP,OU=Service Accounts,OU=[My OU Removed],DC=[My DC removed],DC=com' ...but it is still not working... I saw somewhere to run "/opt/gitlab/embedded/service/gitlab-rails/bin/bundle exec rake gitlab:ldap:check[100] RAILS_ENV=production" as the "git" user and here is the output from that: > (in /opt/gitlab/embedded/service/gitlab-rails) > Checking LDAP ... > LDAP users with access to your GitLab server (only showing the first 100 > results) > Checking LDAP ... Finished I'm not sure what to do next to troubleshoot. Can anyone give me some pointers? I can't put the user back into the "Corporate" OU due to a new security policy. Thanks!!! -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/a784e44d-1a95-4d4b-89b0-166d4fe296e9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.