One thing that can be a bit tricky is that - even if you change the connection info in Config.pm - the *results* are cached for a couple of minutes. If you search for 'John", then remove the customer backend configuration, then do the same search for "John" again OTRS will present you the cached results.
You can use the bin/CacheDelete.pl script to remove the cache. hth, Mike. On Wed, Nov 3, 2010 at 4:18 PM, Ronaldo Richieri <[email protected]> wrote: > Hi, > > I'm trying to chance a Config.pm file to update some Auth parameters. OTRS > searchs Customer on a AD Server. There are configurations for it but even if > a remove the Config.pm file, the system still finding the customer inĀ the > AD via LDAP authentication. > > Is this configuration cached somewhere? Is there a way to force OTRS to read > Config.pm settings as default or something like that? > > Thanks, > > Ronaldo Richieri > (15) 8818-2009 > http://richieri.com > skype: rrichieri > twitter: @richieri > > > --------------------------------------------------------------------- > OTRS mailing list: otrs - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/otrs > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs > --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
