[deployment-guide/comm-rel: 694/727] Modified the LDAP Terminology section.
Jaromir Hradilek
jhradile at fedoraproject.org
Tue Oct 19 13:24:08 UTC 2010
commit 3bc746e0e82ea49d5857d2683b5a7d692ebaa681
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Wed Sep 29 15:57:29 2010 +0200
Modified the LDAP Terminology section.
.../Lightweight_Directory_Access_Protocol_LDAP.xml | 90 ++++++++++----------
1 files changed, 45 insertions(+), 45 deletions(-)
---
diff --git a/en-US/Lightweight_Directory_Access_Protocol_LDAP.xml b/en-US/Lightweight_Directory_Access_Protocol_LDAP.xml
index 2a8e95c..551dac4 100644
--- a/en-US/Lightweight_Directory_Access_Protocol_LDAP.xml
+++ b/en-US/Lightweight_Directory_Access_Protocol_LDAP.xml
@@ -23,6 +23,51 @@
<para>
The LDAP server supports several database systems, which gives administrators the flexibility to choose the best suited solution for the type of information they are planning to serve. Because of a well-defined client <firstterm>Application Programming Interface</firstterm> (<acronym>API</acronym>), the number of applications able to communicate with an LDAP server is numerous, and increasing in both quantity and quality.
</para>
+ <section id="s1-ldap-terminology">
+ <title>LDAP Terminology</title>
+ <para>
+ The following is a list of LDAP-specific terms that are used within this chapter:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>entry</term>
+ <listitem>
+ <para>
+ A single unit within an LDAP directory. Each entry is identified by its unique <firstterm>Distinguished Name</firstterm> (<acronym>DN</acronym>).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>attribute</term>
+ <listitem>
+ <para>
+ Information directly associated with an entry. For example, if an organization is represented as an LDAP entry, attributes associated with this organization might include an address, a fax number, etc. Similarly, people can be represented as entries with common attributes such as personal telephone number or email address.
+ </para>
+ <para>
+ While certain attributes are optional, other are required. Required attributes are specified using the <option>objectClass</option> definition, and can be found in schema files located in the <filename class="directory">/etc/openldap/schema/</filename> directory.
+ </para>
+ <para>
+ The assertion of an attribute and its corresponding value is also referred to as a <firstterm>Relative Distinguished Name</firstterm> (<acronym>RDN</acronym>). Unlike distinguished names that are unique globally, a relative distinguished name is only unique per entry.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>LDIF</term>
+ <listitem>
+ <para>
+ The <firstterm>LDAP Data Interchange Format</firstterm> (<acronym>LDIF</acronym>) is a plain text representation of an LDAP entry. It takes the following form:
+ </para>
+ <screen><optional><replaceable>id</replaceable></optional> dn: <replaceable>distinguished_name</replaceable>
+<replaceable>attribute_type</replaceable>: <replaceable>attribute_value</replaceable>
+<replaceable>attribute_type</replaceable>: <replaceable>attribute_value</replaceable>
+…</screen>
+ <para>
+ The optional <replaceable>id</replaceable> is a number determined by the application that is used to edit the entry. Each entry can contain as many <replaceable>attribute_type</replaceable> and <replaceable>attribute_value</replaceable> pairs as needed, as long as they are all defined in a corresponding schema file. A blank line indicates the end of an entry.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
<section id="s1-ldap-v3">
<title>OpenLDAP Features</title>
<para>
@@ -62,51 +107,6 @@
</itemizedlist>
</section>
</section>
- <section id="s1-ldap-terminology">
- <title>LDAP Terminology</title>
- <para>
- Any discussion of LDAP requires a basic understanding of a set of LDAP-specific terms:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <firstterm>entry</firstterm> — A single unit within an LDAP directory. Each entry is identified by its unique <firstterm>Distinguished Name (DN)</firstterm>.
- </para>
- </listitem>
- <listitem>
- <para>
- <firstterm>attributes</firstterm> — Information directly associated with an entry. For example, an organization could be represented as an LDAP entry. Attributes associated with the organization might include a fax number, an address, and so on. People can also be represented as entries in an LDAP directory, with common attributes such as the person's telephone number and email address.
- </para>
- <para>
- Some attributes are required, while other attributes are optional. An <firstterm>objectclass</firstterm> definition sets which attributes are required for each entry. Objectclass definitions are found in various schema files, located in the <filename>/etc/openldap/schema/</filename> directory. For more information, refer to <xref linkend="s1-ldap-files-schemas" />.
- </para>
- <para>
- The assertion of an attribute and its corresponding value is also referred to as a <firstterm>Relative Distinguished Name</firstterm> (RDN). An RDN is only unique per entry, whereas a DN is globally unique.
- </para>
- </listitem>
- <listitem>
- <para>
- <firstterm>LDIF</firstterm> — The <firstterm>LDAP Data Interchange Format</firstterm> (LDIF) is an ASCII text representation of LDAP entries. Files used for importing data to LDAP servers must be in LDIF format. An LDIF entry looks similar to the following example:
- </para>
- <screen>[<<replaceable>id</replaceable>>] dn: <<replaceable>distinguished name</replaceable>>
-<<replaceable>attrtype</replaceable>>: <<replaceable>attrvalue</replaceable>>
-<<replaceable>attrtype</replaceable>>: <<replaceable>attrvalue</replaceable>>
-<<replaceable>attrtype</replaceable>>: <<replaceable>attrvalue</replaceable>></screen>
- <para>
- Each entry can contain as many <command><<replaceable>attrtype</replaceable>>: <<replaceable>attrvalue</replaceable>></command> pairs as needed. A blank line indicates the end of an entry.
- </para>
- <warning>
- <title>Caution</title>
- <para>
- All <command><<replaceable>attrtype</replaceable>></command> and <command><<replaceable>attrvalue</replaceable>></command> pairs <emphasis>must</emphasis> be defined in a corresponding schema file to use this information.
- </para>
- </warning>
- <para>
- Any value enclosed within a <command><</command> and a <command>></command> is a variable and can be set whenever a new LDAP entry is created. This rule does not apply, however, to <command><<replaceable>id</replaceable>></command>. The <command><<replaceable>id</replaceable>></command> is a number determined by the application used to edit the entry.
- </para>
- </listitem>
- </itemizedlist>
- </section>
<section id="s1-ldap-daemonsutils">
<title>OpenLDAP Daemons and Utilities</title>
<para>
More information about the docs-commits
mailing list