The basic form of an LDIF entry is as follows:
[id] dn: distinguished name attrtype: attrvalue attrtype: attrvalue ...where id is the optional entry ID (a positive decimal number). Normally, you would not supply the id, allowing the database creation tools to do that for you. The ldbmcat program, however, produces an LDIF format that includes id so that new indexes created will be consistent with the existing database. A line may be continued by starting the next line with a single space or tab character. For example:
dn: cn=Barbara J Jensen, o=University of Michi gan, c=USMultiple attribute values are specified on separate lines, for example:
cn: Barbara J Jensen cn: Babs JensenIf an attrvalue contains a non-printing character, or begins with a space or a colon (:), the attrtype is followed by a double colon and the value is encoded in base 64 notation. For example, the value `` begins with a space'' would be encoded like the following:
cn:: IGJlZ2lucyB3aXRoIGEgc3BhY2U=Multiple entries within the same LDIF file are separated by blank lines.
dn: cn=Barbara J Jensen, o=University of Michi gan, c=US cn: Barbara J Jensen cn: Babs Jensen objectclass: person sn: JensenNotice that the jpegPhoto in Jennifer Jensen's entry is encoded using base 64.dn: cn=Bjorn J Jensen, o=University of Michi gan, c=US cn: Bjorn J Jensen cn: Bjorn Jensen objectclass: person sn: Jensen
dn: cn=Jennifer J Jensen, o=University of Michi gan, c=US cn: Jennifer J Jensen cn: Jennifer Jensen objectclass: person sn: Jensen jpegPhoto:: /9j/4AAQSkZJRgABAAAAAQABAAD/2wBDABALD A4MChAODQ4SERATGCgaGBYWGDEjJR0oOjM9PDkzODdASFxOQ ERXRTc4UG1RV19iZ2hnPk1xeXBkeFxlZ2P/2wBDARESEhgVG ...
The SLAPD and SLURPD Administrator's Guide