Hi Stefanie, I tried reproducing the problem with nulls but couldn't, neither with flat nor hierarchical LDAP.
The only thing that I see potentially wrong with your config is that you set email_field = mail, while it needs to be email_field = uid. This is an unfortunate assumption of the DSpace authn system (login=email) that doesn't sit well with LDAP, but fixing it would be quite an extensive change, so try this workaround for now. The consequence is that your LDAP users won't have a valid email address in DSpace, so subscriptions won't work for them. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ 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
