1 .TH LDIF 5 "22 September 1998" "OpenLDAP LDVERSION"
3 ldif \- LDAP Data Interchange Format
5 The LDAP Data Interchange Format (LDIF) is used to represent LDAP
6 entries in text form. The
8 tools can be used to convert from LDIF format to the LDBM format
13 tool can be used to do the reverse conversion. See "The SLAPD and
14 SLURPD Administrator's Guide" for more information on this format and
17 The basic form of an LDIF entry is:
22 dn: <distinguished name>
23 <attrtype>: <attrvalue>
24 <attrtype>: <attrvalue>
29 where <id> is the optional entry ID (a positive decimal number).
30 Normally, you would not supply the <id>, allowing the database creation
31 tools to do that for you. The
33 program, however, produces an LDIF format that includes <id> so that
34 new indexes created will be consistent with the existing database. A
35 line may be continued by starting the next line with a single space or
40 dn: cn=Barbara J Jensen, o=University of Michi
45 Multiple attribute values are specified on separate lines, e.g.,
54 If an <attrvalue> contains a non-printing character, or begins with a
55 space or a colon ':', the <attrtype> is followed by a double colon and
56 the value is encoded in base 64 notation. e.g., the value " begins with
57 a space" would be encoded like this:
61 cn:: IGJlZ2lucyB3aXRoIGEgc3BhY2U=
65 Multiple entries within the same LDIF file are separated by blank
68 Here is an example of an LDIF file containing three entries.
72 dn: cn=Barbara J Jensen, o=University of Michi
79 dn: cn=Bjorn J Jensen, o=University of Michi
86 dn: cn=Jennifer J Jensen, o=University of Michi
92 jpegPhoto:: /9j/4AAQSkZJRgABAAAAAQABAAD/2wBDABALD
93 A4MChAODQ4SERATGCgaGBYWGDEjJR0oOjM9PDkzODdASFxOQ
94 ERXRTc4UG1RV19iZ2hnPk1xeXBkeFxlZ2P/2wBDARESEhgVG
99 Notice that the jpegPhoto in Jennifer Jensen's entry is encoded using
107 "The SLAPD and SLURPD Administrator's Guide"
110 is developed and maintained by The OpenLDAP Project (http://www.openldap.org/).
112 is derived from University of Michigan LDAP 3.3 Release.