Hi Darren, I don't think this can be DSpace's fault. Although DSpace can create an eperson on the first login via LDAP (if autoregister is set to true), it only means that a row in the eperson table is created. The password is not stored in DSpace and the user is always authenticated by trying to bind to LDAP with the specified username/password.
If I were you, I'd take a look at your LDAP infrastructure. If you have some kind of replication set up or if you're using custom code to change the password in multiple systems (LDAP being just one of them), the changed password may not yet have propagated to the LDAP server DSpace uses. So try to bind the user using e.g. the ldapsearch utility or any other LDAP client. My bet is that the LDAP server still has the old password. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
