Problem solved: It was way simpler than I thought: In the authentication-ldap.cfg file, the authentication-ldap.search.user was set to: authentication-ldap.search.user = cn=Leitor2\,dc=ufrgs\,dc=br But the correct user was: authentication-ldap.search.user = uid=Leitor2\,dc=ufrgs\,dc=br As soon as we changed this, DSpace was able to set the EPerson email correctly and everything got back to normal. Thanks for trying to help, Michael.
Em sexta-feira, 8 de maio de 2026 às 13:55:43 UTC-3, Michael Plate escreveu: > Hi Guilherme, > > I'm out of imagination on that. > > > Am 06.05.26 um 22:42 schrieb Guilherme Iepsen: > > Hi Michael, > > > > The ldapsearch is working fine with any user. > > I can retrieve the "mail" attribute perfectly using ldapsearch. But it > > seems that's not possible through DSpace. > > are there multiple "mail" attributes - maybe this is a problem ? E.g., I > have a bunch of that, so we use userPreferredEmail instead. > > Another possibility is to switch to debug mode in config/log4j2.xml and > try the logs, but this is painful. > > Michael > > -- All messages to this mailing list should adhere to the Code of Conduct: https://lyrasis.org/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/17e56c86-cd86-4447-ab6b-f616b157a2e5n%40googlegroups.com.
