Red Hat Directory Server 8.0 Administrator's Guide

• Only one attribute can be specified on which the uniqueness check will be performed.
• It is possible to specify several DNs of suffixes or subtrees in which to perform the
uniqueness check by incrementing the nsslapd-pluginarg attribute suffix by one each time.
The variable components of the Attribute Uniqueness Plug-in syntax are described in
Table 18.1, “Attribute Uniqueness Plug-in Variables”.
Use the following syntax to specify to perform the uniqueness check below an entry containing
a specified object class:
dn: cn=descriptive_plugin_name,cn=plugins,cn=config
...
nsslapd-pluginEnabled: state
nsslapd-pluginarg0: attribute=attribute_name
nsslapd-pluginarg1: markerObjectClass=objectclass1
nsslapd-pluginarg2: requiredObjectClass=objectclass2
...
• Any value can be given to the cn attribute to name the plug-in. The name should be
descriptive.
• The cn attribute does not contain the name of the attribute which is checked for uniqueness.
• Only one attribute can be specified on which the uniqueness check will be performed.
• If the nsslapd-pluginarg0 attribute begins with attribute=attribute_name, then the server
expects the nsslapd-pluginarg1 attribute to include a markerObjectClass value.
The variable components of the attribute uniqueness plug-in syntax are described in Table 18.1,
“Attribute Uniqueness Plug-in Variables”.
Variable Definition
descriptive_plugin_name Specifies the name of this instance of the
Attribute Uniqueness Plug-in. It is not required
that the name of the attribute for which to
ensure uniqueness be included, but it is
advisable. For example, cn=mail
uniqueness,cn=plugins,cn=config.
state Defines whether the plug-in is enabled or
disabled. Acceptable values are on or off.
See Section 4.3.1, “Turning the Plug-in On or
Off” for more information.
attribute_name The name of the attribute for which to ensure
unique values. Only one attribute can be
named.
Attribute Uniqueness Plug-in Syntax
505