Continuing Lines In Ldif; Representing Binary Data - Red Hat DIRECTORY SERVER 8.0 - ADMINISTRATION Administration Manual

Appendix A. LDAP Data Interchange Format
Field
objectClass: object_class
attribute_type
[subtype]
attribute_value
Table A.1. LDIF Fields
NOTE
The LDIF syntax for representing a change to an entry in the directory is different from
the syntax described in
directory entries, see
A.2. Continuing Lines in LDIF
In LDIF files, a line can be broken and continued (called folded) by indenting the continued portion of
the line by exactly one space. For example, the following two statements are identical:
dn: cn=Jake Lupinski,dc=example,dc=com
dn: cn=Jake Lup
inski, dc=exa
mple,dc=com
It is not required to break and continue LDIF lines. However, doing so may improve the readability of
the LDIF file. The usual convention is that an LDIF file does not contain more than 78 columns of text.
A.3. Representing Binary Data
Binary data, such as a JPEG image, is represented in LDIF using one of two methods, standard LDIF
notation or base-64 encoding.
468
Definition
Specifies an object class to use with this entry.
The object class identifies the types of attributes,
or schema, allowed and required for the entry.
See
for information on customizing the schema.
Specifies a descriptive attribute to use with the
entry. The attribute should be defined either
in the schema. See
Directory Schema
the schema.
Optional. Specifies subtype, language, binary,
or pronunciation. Use this tag to identify the
language in which the corresponding attribute
value is expressed or whether the attribute
value is binary or a pronunciation of an attribute
value. For information on attribute subtypes, see
Section 2.1.3.8, "Adding an Attribute
For a complete list of the supported subtypes
tags, see
Subtypes".
Specifies the attribute value to be used with the
attribute type.
Table A.1, "LDIF Fields". For information on using LDIF to modify
Chapter 2, Creating Directory
Chapter 9, Extending the Directory Schema
Chapter 9, Extending the
for information on customizing
Table D.2, "Supported Language
Entries.
Subtype".