A recent changes made in our campus ldap service has caused us some difficulty in configuring ldap for dspace.
Our instance of dspace uses ldap to connect to the campus active directory instance to authenticate users. The ldap active directory server has recently moved to four servers with a gateway to load balance and provide fail-over. Our ldap domain is ads.uwaterloo.ca, but the hostname of the gateway is ldap.ads.uwaterloo.ca. In the wake of this change we changed the configuration file for dspace to: ldap.provider_url = ldap://ldap.ads.uwaterloo.ca but this broke our authentication. As best we can determine, this change finds the gateway but tries to bind the user as [EMAIL PROTECTED] instead of [EMAIL PROTECTED] (We are not sure that this is the underlying behavior, but we get an authorization error in the dspace logs with this configuration.) ldap.provider_url = ldap://ads.uwaterloo.ca works and binds correctly, but it points to one of the four servers, so we lose the better availability provided by the gateway. Is there anyway to be more fine grained with ldap configuration for dspace? Can we point to the ldap.ads.uwaterloo.ca gateway but bind as [EMAIL PROTECTED] Any help or pointers to the necessary info would be greatly appreciated. Chris Gray Library Systems University of Waterloo Library ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
