LDAP and timeLimit Value
Ryan Tapp
Ryan.Tapp at csulb.edu
Mon Dec 3 18:45:24 EST 2018
I believe I've resolved my issue with slow ldap performance and Peter, channeling Scott, basically gave me the answer in the very beginning: [or (as Scott often says) your configuration is not what you think it is].
In our environment cn and uid have the same value. So leaving the "default" search filter to (uid=$resolutionContext.principal) works but is slow. I earlier noted slightly less than 1 second for each search when ldap was "working". I changed the search filter to (cn=$resolutionContext.principal) and I'm getting the search done in 0.001 seconds. Slight improvement. I never had a reason to change that (or even suspect it was causing issues) so it remained unchanged because it was working.
I became fixated on the timeLimit = 4 (and I'm still seeing that in the searchRequest packet each time) but it's now obviously not a problem in and of itself. I'm still curious where that value is coming from, but I can live with the mystery.
Thanks to everyone who helped, both on and off list. I appreciate the support.
Ryan Tapp
California State University Long Beach
More information about the users
mailing list