On Mon, Jul 29, 2013 at 6:58 AM, Keir Vaughan-Taylor <[email protected]> wrote: > The routine is only executed when a user is an admin user or if the > config allows anonymous search.
Yes, that was the intention. If, however, the previous version allowed your use case (you can get you own information but no-one else's), it is a regression and we should fix it. I thought get-your-own-information worked in the anonymous search scenario, but I have no way of actually testing that. Did you try not to specify search.user and set search.anonymous = true? Could you send us your old authentication-ldap.cfg that used to work? > LDAP servers mostly use a challenge > response system where information for a person is supplied from a netid > (user name) and a correct password. That is; you can get you own > information but no-one else's. As a workaround / supported use case, you could set up search.user to be a new LDAP user with search access to all user's attributes (only those needed by DSpace). Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
