1 .TH LDIF 5 "22 September 1998" "OpenLDAP LDVERSION"
3 .\" Copyright 1998-1999 The OpenLDAP Foundation All Rights Reserved.
4 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 ldif \- LDAP Data Interchange Format
8 The LDAP Data Interchange Format (LDIF) is used to represent LDAP
9 entries in text form. LDAP tools, such as
15 The basic form of an LDIF entry is:
19 dn: <distinguished name>
20 <attrtype>: <attrvalue>
21 <attrtype>: <attrvalue>
22 <attrtype>:: <base64-encoded-value>
28 The value may be specified as ASCII text or as base64 encoded data,
29 or a URL may be provided to the location of the attribute value.
31 A line may be continued by starting the next line with a single space
36 dn: cn=Barbara J Jensen, dc=Open
41 Multiple attribute values are specified on separate lines, e.g.,
50 If an value contains a non-printing character, or begins
51 with a space or a colon ':', the <attrtype> is followed by a
52 double colon and the value is encoded in base 64 notation. e.g.,
53 the value " begins with a space" would be encoded like this:
57 cn:: IGJlZ2lucyB3aXRoIGEgc3BhY2U=
61 If the attribute value is located in a file, the <attrtype> is
62 followed by a ':<' and a file:// URL. e.g., the value contained
63 in the file /tmp/value would be listed like this:
71 Multiple entries within the same LDIF file are separated by blank
74 Here is an example of an LDIF file containing three entries.
78 dn: cn=Barbara J Jensen, dc=OpenLDAP, dc=Org
82 description:< file://tmp/barbara
85 dn: cn=Bjorn J Jensen, dc=OpenLDAP, dc=Org
91 dn: cn=Jennifer J Jensen, dc=OpenLDAP, dc=Org
96 jpegPhoto:: /9j/4AAQSkZJRgABAAAAAQABAAD/2wBDABALD
97 A4MChAODQ4SERATGCgaGBYWGDEjJR0oOjM9PDkzODdASFxOQ
98 ERXRTc4UG1RV19iZ2hnPk1xeXBkeFxlZ2P/2wBDARESEhgVG
103 Notice that the jpegPhoto in Jennifer Jensen's entry is encoded using
110 "The SLAPD and SLURPD Administrator's Guide"
113 is developed and maintained by The OpenLDAP Project (http://www.openldap.org/).
115 is derived from University of Michigan LDAP 3.3 Release.