I have implemented LDAP authentication for logging into DSpace 1.5.2, and am finding that it works fine for 3-5 days or so, but then fails for all LDAP login attempts. I have to restart Apache/Tomcat in order to get it going again, and even then it sometimes requires several restarts.
The DSpace log shows a Java error of "Connection refused" when this happens, but this may not be a true reflection of the problem. Is there any extra logging on the DSpace side that I can do to try and diagnose the problem? Any theories about the cause? Caching of responses or some other memory issue perhaps? Something I should mention is that we use a ldap.provider_url = ldap://lincoln.ac.nz:389/ which is not an actual server name, but a DNS _SRV record for AD that may return the address of any of 6 LDAP servers - perhaps the LDAP connector that DSpace uses cannot handle that? If so, is ther a way to specify multiple LDAP providers in dspace.cfg tp rpovide reduancy if one fails? Thanks for any help you can give Andrew Andrew White Information Technology Librarian George Forbes Memorial Library PO Box 64 Lincoln University Lincoln 7647 Christchurch, New Zealand p +64 3 321 8542 | f +64 3 325 2944 e [email protected]<mailto:[email protected]> | w library.lincoln.ac.nz<http://library.lincoln.ac.nz/> Lincoln University, Te Whare Wanaka o Aoraki New Zealand's Specialist Land Based University "The contents of this e-mail (including any attachments) may be confidential and/or subject to copyright. Any unauthorised use, distribution, or copying of the contents is expressly prohibited. If you have received this e-mail in error, please advise the sender by return e-mail or telephone and then delete this e-mail together with all attachments from your system."
------------------------------------------------------------------------------
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
