1 .TH SLAPO-UNIQUE 5 "RELEASEDATE" "OpenLDAP LDVERSION"
2 .\" Copyright 2004-2006 The OpenLDAP Foundation All Rights Reserved.
3 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 slapo-unique \- Attribute Uniqueness overlay
10 The Attribute Uniqueness overlay can be used with a backend database such as
12 to enforce the uniqueness of some or all attributes within a subtree. This
13 subtree defaults to the base DN of the database for which the Uniqueness
14 overlay is configured.
16 Uniqueness is enforced by searching the subtree to ensure that the values of
17 all attributes presented with an
22 operation are unique within the subtree.
23 For example, if uniqueness were enforced for the
25 attribute, the subtree would be searched for any other records which also
28 attribute containing the same value. If any are found, the request is
33 options apply to the Attribute Uniqueness overlay.
34 They should appear after the
36 directive and before any subsequent
40 .B unique_base <basedn>
41 Configure the subtree against which uniqueness searches will be invoked.
44 defaults to the base DN of the database for which uniqueness is configured.
46 .B unique_ignore <attribute...>
47 Configure one or more attributes for which uniqueness will not be enforced.
48 If not configured, all non-operational (eg, system) attributes must be
51 list should generally contain the
57 attributes, as these will generally not be unique, nor are they operational
60 .B unique_attributes <attribute...>
61 Specify one or more attributes for which uniqueness will be enforced.
62 If not specified, all attributes which are not operational (eg, system
67 directive above must be unique within the subtree.
70 By default, uniqueness is not enforced for null values. Enabling
72 mode extends the concept of uniqueness to include null values, such that
73 only one attribute within a subtree will be allowed to have a null value.
76 The search key is generated with attributes that are non-operational, not
79 list, and included in the
81 list, in that order. This makes it possible to create interesting and
82 unusable configurations. Usually only one of
86 should be configured; use
88 if the majority of attributes should be unique, and use
90 if only a small set of attributes should be unique.
92 Typical attributes for the
94 directive are intentionally not hardcoded into the overlay to allow for
95 maximum flexibility in meeting site-specific requirements.
99 default slapd configuration file