Mike Peachey wrote: > It is definitely related to the filter. The problem is in UserExists > which ensures that the user actually exists in the user database, and is > run once for each specified database iirc. > > Double, triple and then quadruple check your filter value in the config.
I'm not convinced that the filter value is the config is to blame for this. It hasn't been changed since the initial installation and everything has been working up until a little while ago. I found out what was causing the problem although I still don't know *why* it is a problem. Someone changed the URL to RT in our wiki to be http://rt?user=john_doe so that the username would be set automatically as per the wiki username. Seemed like a smart idea since both authenticate against the same LDAP server. Whenever this URL is used to get to RT the error appears. If I remove ?user=john_doe and log in manually everything works just fine. Does anyone know why this would be? We're using RT 3.8.5 and RT::Authen::ExternalAuth 0.08 My problem is solved for the time being but it would be nice to know why ?user=john_doe causes problems. Thanks, Matt -- Matt Adams Development & Network Services, Cypress Interactive http://cypressinteractive.com, http://edsuite.com _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [email protected] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
