slapo-unique man page on Peanut

Man page or keyword search:  
man Server   7435 pages
apropos Keyword Search (all sections)
Output format
Peanut logo
[printable version]

SLAPO-UNIQUE(5)						       SLAPO-UNIQUE(5)

NAME
       slapo-unique - Attribute Uniqueness overlay

SYNOPSIS
       /etc/openldap/slapd.conf

DESCRIPTION
       The  Attribute  Uniqueness  overlay can be used with a backend database
       such  as	 slapd-bdb(5)  to  enforce  the	 uniqueness  of	 some  or  all
       attributes  within  a  subtree. This subtree defaults to the base DN of
       the database for which the Uniqueness overlay is configured.

       Uniqueness is enforced by searching the subtree to ensure that the val‐
       ues of all attributes presented with an add, modify or modrdn operation
       are unique  within  the	subtree.   For	example,  if  uniqueness  were
       enforced	 for  the uid attribute, the subtree would be searched for any
       other records which also have  a	 uid  attribute	 containing  the  same
       value. If any are found, the request is rejected.

CONFIGURATION
       These  slapd.conf  options  apply  to the Attribute Uniqueness overlay.
       They should appear after the overlay directive.

       unique_base <basedn>
	      Configure the subtree against which uniqueness searches will  be
	      invoked.	The basedn defaults to the base DN of the database for
	      which uniqueness is configured.

       unique_ignore <attribute...>
	      Configure one or more attributes for which uniqueness  will  not
	      be  enforced.   If not configured, all non-operational (eg, sys‐
	      tem) attributes must be unique. Note that the unique_ignore list
	      should   generally   contain  the	 objectClass,  dc,  ou	and  o
	      attributes, as these will generally not be unique, nor are  they
	      operational attributes.

       unique_attributes <attribute...>
	      Specify  one  or	more  attributes  for which uniqueness will be
	      enforced.	 If not specified, all attributes which are not opera‐
	      tional  (eg,  system attributes such as entryUUID ) or specified
	      via the unique_ignore directive above must be unique within  the
	      subtree.

       unique_strict
	      By default, uniqueness is not enforced for null values. Enabling
	      unique_strict mode extends the concept of uniqueness to  include
	      null  values, such that only one attribute within a subtree will
	      be allowed to have a null value.

CAVEATS
       The search key is generated with attributes that	 are  non-operational,
       not  on	the  unique_ignore list, and included in the unique_attributes
       list, in that order. This makes it possible to create  interesting  and
       unusable	  configurations.   Usually   only  one	 of  unique_ignore  or
       unique_attributes should be configured; use unique_ignore if the major‐
       ity of attributes should be unique, and use unique_attributes if only a
       small set of attributes should be unique.

       Typical attributes for the unique_ignore	 directive  are	 intentionally
       not  hardcoded  into  the  overlay  to allow for maximum flexibility in
       meeting site-specific requirements.

FILES
       /etc/openldap/slapd.conf
	      default slapd configuration file

SEE ALSO
       slapd.conf(5).

OpenLDAP 2.3.24			  2006/05/30		       SLAPO-UNIQUE(5)
[top]

List of man pages available for Peanut

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net