Directory Entries in LDIF

Organization Entries in LDIF

Directories often have at least one organization entry. Typically the
organization entry is the first, or topmost entry in the directory. The organization
entry often corresponds to the suffix set for the directory. For example,
a directory defined to use a suffix of o=example.com will
probably have an organization entry named o=example.com.

Specifies the organization object class. This line defines the entry
as an organization.

o:organization_name

Specifies 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

Specifies 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
file that defines an organizational unit entry must appear as follows:

If there is a comma in the DN, the comma must be escaped with a backslash
(\). For example, dn:uid=bjensen,ou=people,o=example.com Bolivia\,S.A.

objectClass: top

Required. Specifies the top object class.

objectClass: person

Specifies the person object class. This object class
specification should be included because many LDAP clients require it during
search operations for a person or an organizational person.

objectClass: organizationalPerson

Specifies the organizationalPerson object class.
This object class specification should be included because some LDAP clients
require it during search operations for an organizational person.

objectClass: inetOrgPerson

Specifies the inetOrgPerson object class. The inetOrgPerson object class is recommended for the creation of an organizational
person entry because this object class includes the widest range of attributes.
The uid attribute is required by this object class, and
entries that contain this object class are named based on the value of the uid attribute.

cn:common_name

Required. Specifies the person’s common name which is the full
name commonly used by the person. For example, cn: Bill Anderson.

sn:surname

Required. Specifies the person’s surname, or last name. For example, sn: Anderson.

list_of_attributes

Specifies the list of optional attributes that you maintain for the
entry.