Priority: Enhancement
Current State: Closed
Released In: n/a
Target Release: n/a
Applies To: Extension
Component: LdapContrib
Branches: trunk
I'm attaching a patch that slightly improves the performance of
LdapContrib 4.30. Rather than splitting, mapping, and joining, it searches and appends the UNKWNGROUP string directly.
--
JayenAshar - 04 Mar 2012
Trying to track down performance issues with
LdapContrib. I've updated my patch, and now I'm looking at some issue where
U2W isn't being cached when $dn matches $data->{"U2DN::$loginName"} (in cacheUserFromEntry). I'm getting warnings like:
- LdapContrib - WARNING: CN=z3142471,OU=People71,OU=IDM_People,OU=IDM,DC=ad,DC=unsw,DC=edu,DC=au clashes with CN=z3142471,OU=People71,OU=IDM_People,OU=IDM,DC=ad,DC=unsw,DC=edu,DC=au on loginName z3142471 ... please configure a unique loginName attribute
- LdapContrib - WARNING: CN=z3142471,OU=People71,OU=IDM_People,OU=IDM,DC=ad,DC=unsw,DC=edu,DC=au clashes with CN=z3142471,OU=People71,OU=IDM_People,OU=IDM,DC=ad,DC=unsw,DC=edu,DC=au on loginName z3142471 ... please configure a unique loginName attribute
- LdapContrib - WARNING: CN=z3142471,OU=People71,OU=IDM_People,OU=IDM,DC=ad,DC=unsw,DC=edu,DC=au clashes with CN=z3142471,OU=People71,OU=IDM_People,OU=IDM,DC=ad,DC=unsw,DC=edu,DC=au on loginName z3142471 ... please configure a unique loginName attribute
- LdapContrib - WARNING: CN=z3195108,OU=People08,OU=IDM_People,OU=IDM,DC=ad,DC=unsw,DC=edu,DC=au clashes with CN=z3195108,OU=People08,OU=IDM_People,OU=IDM,DC=ad,DC=unsw,DC=edu,DC=au on loginName z3195108 ... please configure a unique loginName attribute
- LdapContrib - WARNING: CN=z3195108,OU=People08,OU=IDM_People,OU=IDM,DC=ad,DC=unsw,DC=edu,DC=au clashes with CN=z3195108,OU=People08,OU=IDM_People,OU=IDM,DC=ad,DC=unsw,DC=edu,DC=au on loginName z3195108 ... please configure a unique loginName attribute
- LdapContrib - WARNING: CN=z3195108,OU=People08,OU=IDM_People,OU=IDM,DC=ad,DC=unsw,DC=edu,DC=au clashes with CN=z3195108,OU=People08,OU=IDM_People,OU=IDM,DC=ad,DC=unsw,DC=edu,DC=au on loginName z3195108 ... please configure a unique loginName attribute
(Yes, those DN's match exactly and the loginName attribute (cn) is unique.)
--
JayenAshar - 08 Apr 2012
The above bogus message has been fixed in 4.40.
Will add the above performance fix and do the same for UNKWNUSERS to the next release.
--
MichaelDaum - 26 Jun 2012