It seems allright, you're using id_field correctly (assuming all else is correct). You just didn't respond which authentication plugin you used. You should use LDAPHierarchicalAuthentication, not LDAPAuthentication, otherwise the initial bind would be ignored and an anonymous search tried, which would be a problem if the mail attribute is not searchable for anonymous users.
If that's not the problem, here's what I'd try next: 1) Use the ldapsearch tool to try to connect to LDAP from the DSpace machine. Start with this: ldapsearch -h your_ldap.com -D "cn=admin,dc=myorg,dc=edu" -W -L "([email protected])" and see if it finds the record for you. That's essentially what your configuration tells DSpace to use. If not, try tweaking the parameters. 2) Use wireshark or tshark to watch the LDAP conversation (limit capture to the IP of your LDAP), this should definitely tell you what parameters it uses and give you a clue why it doesn't work. You will be able to use Wireshark without any advanced configuration because you're using the plain LDAP protocol. When you have it working, I strongly suggest you to use LDAP in the TLS encapuslation (or at least LDAPS, but that one is less secure). Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
