Netscape NETSCAPE DIRECTORY SERVER 6.02, Administrator'S Manual

Page: 495 / 568

Specifying Directory Entries Using LDIF
Appendix A LDAP Data Interchange Format 495
Specifying Organizational Unit Entries
Organizational unit entries are often used to represent major branch points, or
subdirectories, in your directory tree. They correspond to major, reasonably static
entities within your enterprise, such as a subtree that contains people, or a subtree
that contains groups. However, the organizational unit attribute that is contained
in the entry may also represent a major organization within your enterprise, such
as marketing or engineering.
There is usually more than one organizational unit, or branch point, within a
directory tree. For information on how to design your directory tree, see the
Netscape Directory Server Deployment Guide.
The LDIF that you specify to define an organizational unit entry must appear as
follows:
dn:
distinguished_name
objectClass: top
objectClass: organizationalUnit
ou:
organizational_unit_name
list_of_optional_attributes
...
The following is a sample organizational unit entry in LDIF format:
dn: ou=people, dc=example,dc=com
objectclass: top
objectclass: organizationalUnit
ou: people
description: Fictional organizational unit for example purposes
Table A-3 defines each element of the LDIF-formatted organizational unit entry.
Table A-3
LDIF Elements in Organizational Unit Entries
LDIF Element Description
dn: distinguished_name Specifies the distinguished name for the entry. A DN
is required. If there is a comma in the DN, the comma
must be escaped with a backslash (\). For example:
dn: ou=people,o=example.com
Bolivia\,S.A.
objectClass: top Required. Specifies the
top
object class.
objectClass: organizationalUnit Specifies the
organizationalUnit
object class.
This line defines the entry as an organizationalUnit.
See the Netscape Directory Server Schema Reference for a
list of the attributes you can use with this object class.