Red Hat Directory Server 8.0 Configuration, Command, and File Reference

NOTE
The dse.ldif file does not contain every attribute in cn=config. If the attribute
has not been set by the administrator and has a default value, the server will not
write it to dse.ldif. To see every attribute in cn=config, use ldapsearch.
1.2.1. Configuration Attributes
Within a configuration entry, each attribute is represented as an attribute name. The value of the
attribute corresponds to the attribute's configuration.
The following code sample is an example of part of the dse.ldif file for a Directory Server. The
example shows, among other things, that schema checking has been enabled; this is
represented by the attribute nsslapd-schemacheck, which takes the value on.
dn: cn=config
objectclass: top
objectclass: extensibleObject
objectclass: nsslapdConfig
nsslapd-accesslog-logging-enabled: on
nsslapd-enquote-sup-oc: off
nsslapd-localhost: phonebook.example.com
nsslapd-schemacheck: on
nsslapd-port: 389
nsslapd-localuser: nobody
...
1.2.2. Configuration of Plug-in Functionality
The configuration for each part of Directory Server plug-in functionality has its own separate
entry and set of attributes under the subtree cn=plugins,cn=config. The following code
sample is an example of the configuration entry for an example plug-in, the Telephone Syntax
plug-in.
dn: cn=Telephone Syntax,cn=plugins,cn=config
objectclass: top
objectclass: nsSlapdPlugin
objectclass: extensibleObject
cn: Telephone Syntax
nsslapd-pluginType: syntax
nsslapd-pluginEnabled: on
Some of these attributes are common to all plug-ins, and some may be particular to a specific
plug-in. Check which attributes are currently being used by a given plug-in by performing an
How the Server Configuration Is Organized
7