Red Hat Directory Server 8.0 Administrator's Guide

3. Create a sub suffix for groups under this root suffix using ldapmodify to add the sub suffix
entry:
dn: cn=ou=groups,dc=example,dc=com,cn=mapping tree,cn=config
objectclass: top
objectclass: extensibleObject
objectclass: nsMappingTree
nsslapd-state: backend
nsslapd-backend: GroupData
nsslapd-parent-suffix: "dc=example,dc=com"
cn: ou=groups,dc=example,dc=com
NOTE
To maintain suffixes using the Directory Server Console, respect the same
spacing used to name the root and sub suffixes in the command line. For
example, if a root suffix is named ou=groups ,dc=example,dc=com, with two
spaces after groups, any sub suffixes created under this root will need to specify
two spaces after ou=groups, as well.
The following table describes the attributes used to configure a suffix entry:
Attribute Name Value
dn Defines the DN for the suffix. The DN is
contained in quotes. The value entered takes
the form
cn="dc=domain,dc=com",cn=mapping
tree, cn=config. This attribute is required.
cn Defines the relative DN (RDN) of the entry.
This attribute is required.
objectclass Tells the server that the entry is root or sub
suffix entry. It always takes the value
nsMappingTree. This attribute is required.
nsslapd-state Determines how the suffix handles
operations. This attribute takes the following
values:
backend: The backend (database) is used
to process all operations.
Chapter 3. Configuring Directory Databases
52