The following table describes each element of the organization entry.
TABLE 13–2 Organization Entries in LDIF
LDIF Element Description
dn: distinguished_name Required. Species the distinguished name for the entry.
objectClass: top Required. Species the top object class.
objectClass: organization Species the organization object class. This line defines the entry
as an organization.
o: organization_name Species the organization’s name. If the organization name
includes a comma, you must escape the comma by a single
backslash or the entire organization argument must be enclosed
in quotation marks. However, if you are working with a UNIX
shell, you must also escape the backslash. Therefore, you must
use two back slashes. For example, to set the suffix to
example.com Bolivia, S.A. you would enter o: example.com
Bolivia\, S.A..
list_of_attributes Species the list of optional attributes that you want to maintain
for the entry.
Organizational Unit Entries in LDIF
In a directory tree, an organizational unit represents a major subdirectory. A directory tree
usually contains more than one organizational unit. An LDIF le that defines an organizational
unit entry must appear as follows:
dn: distinguished_name
objectClass: top
objectClass: organizationalUnit
ou: organizational_unit_namelist_of_optional_attributes...
The following example shows an organizational unit entry in LDIF format:
dn: ou=people, o=example.com
objectclass: top
objectclass: organizationalUnit
ou: people
description: Fictional organizational unit for example purposes
The following table defines each element of the organizational unit entry.