[Date Prev][Date Next] [Chronological] [Thread] [Top]

(ITS#4066) Uniqueness overlay incorrectly checks for dupes with MODs outside of its seach base

Full_Name: Quanah Gibson-Mount
Version: HEAD 2005-10-04
OS: Solaris 8
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (

In researching a different issue, I had debug logging up on my server.  While
examining the logs, I noticed that there was time spent in the uniqueness
overlay that shouldn't have been.  My uniqueness overlay is configured as:

# Uniqueness Overlay
overlay unique
unique_base cn=people,dc=stanford,dc=edu
unique_attributes suunivid suproxycardnumber sucardnumber suuniqueidentifier

So it should look at anything that does MODs to things under
cn=people,dc=stanford,dc=edu.  However, I was making MODs to
"cn=accounts,dc=stanford,dc=edu".  This shows:

<= entry_decode(uid=XXXXX,cn=Accounts,dc=Stanford,dc=edu)
==> unique_modify <uid=XXXXXX,cn=Accounts,dc=stanford,dc=edu>
=> unique_modify (|)
put_filter: "(|)"
put_filter: OR
put_filter_list ""
=> bdb_search
search_candidates: base="cn=people,dc=stanford,dc=edu" (0x00000005) scope=2
=> bdb_dn2idl("cn=people,dc=stanford,dc=edu")
bdb_idl_fetch_key: @cn=people,dc=stanford,dc=edu
<= bdb_dn2idl: id=-1 first=5 last=367363
=> bdb_equality_candidates (objectClass)
=> key_read
bdb_idl_fetch_key: [b49d1940]
<= bdb_index_read: failed (-30990)
<= bdb_equality_candidates: id=0, first=0, last=0
bdb_search_candidates: id=0 first=5 last=0
bdb_search: no candidates
send_ldap_result: conn=0 op=10 p=3
send_ldap_result: err=0 matched="" text=""
=> unique_search found 0 records

There is obviously no reason here for it to go poking around in the people tree
when the MOD is in the account tree...