LDAP settings not working for CollabNet Subversion server

Posted on 2011-05-04
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://,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
    LVL 5

    Accepted Solution

    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

    DAP Login Attribute:    sAMAccountName

    did the trick :)

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Why You Should Analyze Threat Actor TTPs

    After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

    Suggested Solutions

    The use of stolen credentials is a hot commodity this year allowing threat actors to move laterally within the network in order to avoid breach detection.
    PRTG Network Monitor lets you monitor your bandwidth usage, so you know who is using up your bandwidth, and what they're using it for.
    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…
    This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor ( If you're looking for how to monitor bandwidth using netflow or packet s…

    779 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

    Need Help in Real-Time?

    Connect with top rated Experts

    12 Experts available now in Live!

    Get 1:1 Help Now