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

(ITS#4876) Multiple levels of uniqueness

Full_Name: Quanah Gibson-Mount
Version: 2.3.33
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (

In using the uniqueness overlay, I found there are times I want to apply
uniqueness rules differently based on (sub)tree.  For example, I might like
something along these lines where the db starts at dc=stanford,dc=edu:

overlay unique
unique_base dc=stanford,dc=edu
unique_attributes krb5PrincipalName suRegID

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

overlay unique
unique_base cn=accounts,dc=stanford,dc=edu
unique_attributes uid

However, I found in testing this, that any instantiation of the uniqueness
overlay past the first one is ignored (i.e., not applied to writes).

I think being able to do this is useful, becase I only want the uniqueness
overlay to intercede when the write applies to the particular (sub)tree where it
is necessary to enforce it.

It may be worthwhile to update the syntax for the uniqueness overlay to behave
more like the valsort overlay, where each attribute defines which tree it is
applying weights to, like:

overlay valsort
valsort-attr ou cn=people,dc=stanford,dc=edu weighted
valsort-attr suAffiliation cn=people,dc=stanford,dc=edu weighted
valsort-attr suDisplayAffiliation cn=people,dc=stanford,dc=edu weighted