Defining Directories Using LDIFAppendix A LDAP Data Interchange Format 497Defining Directories Using LDIFYou can define the contents of an entire directory using LDIF. Using LDIF is anefficient method of directory creation when you have many entries to add to thedirectory.Table A-4 LDIF Elements in Person EntriesLDIF Element Descriptiondn: distinguished_name Specifies the distinguished name for the entry. A DN isrequired. If there is a comma in the DN, the comma must beescaped with a backslash (\). For example,dn:uid=bjensen,ou=people,o=example.comBolivia\,S.A.objectClass: top Required. Specifies the top object class.objectClass: person Specifies the person object class. This object classspecification should be included because many LDAPclients require it during search operations for a person or anorganizational person.objectClass:organizationalPersonSpecifies the organizationalPerson object class. Thisobject class specification should be included because someLDAP clients require it during search operations for anorganizational person.objectClass: inetOrgPerson Specifies the inetOrgPerson object class. TheinetOrgPerson object class is recommended for thecreation of an organizational person entry because thisobject class includes the widest range of attributes. The uidattribute is required by this object class, and entries thatcontain this object class are named based on the value of theuid attribute. See the Netscape Directory Server SchemaReference for a list of the attributes you can use with thisobject class.cn: common_name Specifies the person’s common name which is the full namecommonly used by the person. For example, cn: BillAnderson. At least one common name is required.sn: surname Specifies the person’s surname, or last name. For example,sn: Anderson. A surname is required.list_of_attributes Specifies the list of optional attributes that you maintain forthe entry. See the Netscape Directory Server Schema Referencefor a list of the attributes you can use with this object class.
