[Last Call] Learn how to a build a cloud-first strategyRegister Now


LDAP settings not working for CollabNet Subversion server

Posted on 2011-05-04
Medium Priority
1 Endorsement
Last Modified: 2012-06-27
Hi there

We are trying to setup a new Subversion server from CollabNet.

In the Server configuration under Authorization the LDAP setup is configured.

LDAP Security Level:   NONE
LDAP Server Host:    Our Domain Controller
LDAP Server Port:    389
LDAP Base DN:    CN=Schema,CN=Configuration,DC=corp,DC=yr,DC=com
LDAP Bind DN:      Domain\MyUserName
LDAP Bind Password:      MyPassword
LDAP Login Attribute:    Empty (uid will be matched)
LDAP Search Scope:   sub
LDAP Filter:    Empty
As I read the help and Collabnet ressources the above is setup correctly but I keep getting errors in the log that look like this:

[Mon May 02 21:25:15 2011] [info] [client] [11844] auth_ldap authenticate: user steensgaardm authentication failed; URI /svn/dev [LDAP: ldap_simple_bind_s() failed][Server Down]

I have tried to change the LDAP Base DN to include the entire domain name like this:

But then I get this error:

[Wed May 04 22:45:58 2011] [debug] mod_authnz_ldap.c(379): [client] [16924] auth_ldap authenticate: using URL ldap://cphebtdc01.emea.corp.yr.com/OU=EMEA-WUN-CPH-EBT,OU=EMEA-WUN-CPH,OU=EMEA-WUN,DC=emea,DC=corp,DC=yr,DC=com?uid?sub

[Wed May 04 22:45:58 2011] [info] [client] [16924] auth_ldap authenticate: user emea\\petersent authentication failed; URI /svn/ [User not found][No Such Object]

[Wed May 04 22:45:58 2011] [client] user emea\\petersent not found: /svn/

Any help would be greatly appreciated as I'm not what one might call well versed in the Intricasies of LDAP :)

Best Regards
Question by:Panthom

Accepted Solution

PFoeckeler earned 2000 total points
ID: 35814005
You use the AD schema partition as an LDAP Base DN, this looks strange, please try again with you Domain DN as the "LDAP Base DN".....and continue to use "MyDomain\MyUser" as the "LDAP Bind DN". MYbe it should be a good idead to set a default LDAP filter also.. :

LDAP Base DN:    DC=corp,DC=yr,DC=com
LDAP Bind DN:      Domain\MyUserName
LDAP Filter:    (objectClass=*)

another additional idea: use the AD logon name attribute for the "LDAP Login Attribute":

DAP Login Attribute:    sAMAccountName

hope that helps

Author Closing Comment

ID: 35832173
DAP Login Attribute:    sAMAccountName

did the trick :)

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Join Greg Farro and Ethan Banks from Packet Pushers (http://packetpushers.net/podcast/podcasts/pq-show-93-smart-network-monitoring-paessler-sponsored/) and Greg Ross from Paessler (https://www.paessler.com/prtg) for a discussion about smart network …
Use of TCL script on Cisco devices:  - create file and merge it with running configuration to apply configuration changes
Viewers will learn how to properly install and use Secure Shell (SSH) to work on projects or homework remotely. Download Secure Shell: Follow basic installation instructions: Open Secure Shell and use "Quick Connect" to enter credentials includi…
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
Suggested Courses

830 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question