Overview of the Attribute Uniqueness Plug-in
530
Red Hat Directory Server Administrator’s Guide • May 2005
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
LDAP_CONSTRAINT_VIOLATION
error to
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.com
, hosts the directories for
example_a.com
and
example_b.com
, when you add an entry such as
uid=jdoe,ou=people,o=example_a,dc=example,dc=com
, you need to
enforce uniqueness only in the
o=example_a,dc=example,dc=com
subtree.
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
uid=jdoe,ou=people,o=example_a,dc=example,dc=com
, you
can enforce uniqueness under the
o=example_a,dc=example,dc=com
subtree
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
, the uniqueness check algorithm locates the entry in the DN
that has this object class (
o=example_a
) and performs the check on all entries
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
objectclass=inetorgperson
.
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.
Summary of Contents for DIRECTORY SERVER 7.1
Page 1: ...Administrator s Guide Red Hat Directory Server Version7 1 May 2005 Updated February 2009 ...
Page 20: ...20 Red Hat Directory Server Administrator s Guide May 2005 Glossary 619 Index 635 ...
Page 22: ...22 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 26: ...26 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 78: ...Maintaining Referential Integrity 78 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 200: ...Assigning Class of Service 200 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 488: ...488 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 528: ...PTA Plug in Syntax Examples 528 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 572: ...572 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 612: ...Examples of LDAP URLs 612 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 634: ...634 Red Hat Directory Server Administrator s Guide May 2005 ...