because we're instantiating the auth class on startup, it has no concept of session state. As a result, we can get into situations where we're looking up the dn of the user 2-3 times per request as we ask for various bits of data. With the new structure, that's now a ldap search request, so it matters. The way to do this is to use a user object that is passed in to all requests, rather than a userid or username. We can cache the dn in there, and not need to look it up again.
The new user object exists and caches ldap.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.