On 13.7.2012, at 8.30, Dominic Malolepszy wrote: >> It caches the passdb lookup. The cache key consists of the given % >> variables in the SQL query. So if your SQL query doesn't contain %n/%u >> then the cache doesn't add per-user entries. > > I had a chance to play around with this in the lab. The cache hit appears to > be returning values that should actually be ignored particularly the username > for the previous cached entry. This is causing it to rewrite the username > using what is in the cache.
The simplest solution would be to just not put username to cache, but I'm worried it might break something else.. So for now I don't think I'm going to change it.
