Red Hat DIRECTORY SERVER 7.1 - ADMINISTRATOR Administrator's Manual page 530

Overview of the Attribute Uniqueness Plug-in
If an update operation applies to an attribute and suffix monitored by the plug-in
and it would cause two entries to have the same attribute value, then the server
terminates the operation and returns an
the client.
The Attribute Uniqueness Plug-in performs a check on:
• A single attribute
• One or several subtrees
If you want to check uniqueness of several attributes, you must create a separate
instance of the plug-in for each attribute you want to check.
You can also configure how the Attribute Uniqueness Plug-in operates:
• It can check every entry in the subtrees you specify.
For example, if your company,
example_a.com
uid=jdoe,ou=people,o=example_a,dc=example,dc=com
enforce uniqueness only in the
You can do this by listing the DN of the subtree explicitly in the UID
Uniqueness Plug-in configuration.
This configuration option is explained in more detail in "Specifying a Suffix or
Subtree," on page 537.
• You can specify an object class pertaining to an entry in the DN of the
updated entry and perform the uniqueness check on all the entries beneath it.
This option is useful in hosted environments. For example, when you add an
entry such as
can enforce uniqueness under the
without listing this subtree explicitly in the configuration but, instead, by
indicating a marker object class. If you specify that the marker object class is
organization
that has this object class (
beneath it.
Additionally, you can specify to check uniqueness only if the updated entry
includes a specified object class. For example, you could specify to perform
the check only if the updated entry includes
This configuration option is explained in more detail in "Using the
markerObjectClass and requiredObjectClass Keywords," on page 538.
If you intend to use the Attribute Uniqueness Plug-in in a replicated environment,
refer to "Replication and the Attribute Uniqueness Plug-in," on page 541.
530 Red Hat Directory Server Administrator's Guide • May 2005
example.com
and
example_b.com
o=example_a,dc=example,dc=com
uid=jdoe,ou=people,o=example_a,dc=example,dc=com
o=example_a,dc=example,dc=com
, the uniqueness check algorithm locates the entry in the DN
o=example_a
LDAP_CONSTRAINT_VIOLATION
, hosts the directories for
, when you add an entry such as
) and performs the check on all entries
objectclass=inetorgperson
error to
, you need to
subtree.
, you
subtree
.