You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@directory.apache.org by bu...@apache.org on 2015/07/06 00:34:38 UTC
svn commit: r957126 [4/18] - in /websites/staging/directory/trunk/content:
./ apacheds/ apacheds/advanced-ug/ apacheds/basic-ug/
apacheds/configuration/ apacheds/kerberos-ug/ api/ api/download/
api/groovy-api/ api/user-guide/ escimo/ fortress/ fortress...
Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/1.1-what-apacheds-is.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/1.1-what-apacheds-is.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/1.1-what-apacheds-is.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="11-what-apache-directory-server-is">1.1 - What Apache Directory Server is</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="11-what-apache-directory-server-is">1.1 - What Apache Directory Server is<a class="headerlink" href="#11-what-apache-directory-server-is" title="Permanent link">¶</a></h1>
<p>This section describes what Apache Directory Server (abbreviated ApacheDS) is, and where it comes from.</p>
<div class="toc">
<ul>
@@ -184,20 +195,20 @@
</li>
</ul>
</div>
-<h2 id="system-vision">System vision</h2>
+<h2 id="system-vision">System vision<a class="headerlink" href="#system-vision" title="Permanent link">¶</a></h2>
<p>ApacheDS 2.0 is an embeddable, extendable, standards compliant, modern LDAP server written entirely in Java, and available under the Apache Software License. Other network protocols like Kerberos and NTP are supported as well (and even more may be added), but basically (and especially for this introduction guide) ApacheDS is an LDAP server.</p>
<p><em>Embeddable</em> means that it is possible to configure, start and stop ApacheDS from other Java components, especially application servers, and the server runs within the same VM. The solution has already been successfully embedded in Apache Geronimo, JBoss, and others. The fact that the server is embeddable is quite interesting, nevertheless you also have the deployment option to run the server standalone, for instance as a Windows service. Perhaps you know this situation from other LDAP servers -- open source (like OpenLDAP) as well as commercial ones (like Sun Java System Directory Server). This guide is dedicated to people that are new to ApacheDS. The guide concentrates on installing, configuring and running ApacheDS in a standalone configuration.</p>
<p><em>Extendable</em> means that the modern architecture of the solution provides many extension points. Write your own partitions to store directory data, interceptors to add functionality, etc. by implementing certain interfaces and plugging them in using Spring.</p>
<p><em>Standard compliant</em> means that ApacheDS 2.0 adheres to all RFCs relevant to LDAPv3. Please note that version 1.0 of the server has been successfully certified by the Open Group in September 2006 ("LDAP certified"). Thus LDAP clients may rightly expect that ApacheDS behaves like they expect.</p>
<p><em>Modern</em> means that ApacheDS aims modernize the LDAP territory, as well as it favors standards compliance. New rich integration tier constructs like LDAP Stored Procedures and Triggers are being built on top of existing standards.</p>
<p><em>Entirely written in Java</em> means that the software compiles and runs on a huge number of hardware and software platforms. Native installers are available for Windows, MacOS and Solaris (both SPARC and intel platform), but in fact the set of possible targets is by far more extensive.</p>
-<h3 id="architectural-overview">Architectural overview</h3>
+<h3 id="architectural-overview">Architectural overview<a class="headerlink" href="#architectural-overview" title="Permanent link">¶</a></h3>
<p><img alt="50k ft architecture" src="images/50k-ft-architecture.png" /></p>
-<h2 id="origin-and-motives">Origin and Motives</h2>
+<h2 id="origin-and-motives">Origin and Motives<a class="headerlink" href="#origin-and-motives" title="Permanent link">¶</a></h2>
<p>Through his experiences with enterprise LDAP directories, Alex Karasulu, realized there is a great need for rich integration tier constructs like LDAP Stored Procedures, Triggers, and Views. In 2001 he set out to alter the OpenLDAP server to offer support for these useful facilities which are present in relational databases but missing in the LDAP world. Alex's attempts failed due to the complexity of the software which was brittle, and difficult to manage. As C code ported to several platforms, the OpenLDAP code base, had several #IFDEF conditional pre-compiler directives that made it difficult to change the code. At this point Alex thought about implementing a new LDAP server in pure Java. Thanks to NIO this was finally possible using the 1.4 JDK. </p>
<p>In October 2002 Alex Karasulu founded and registered the <a href="http://sourceforge.net/projects/ldapd">LDAPd</a> project at SourceForge.net. LDAPd was a a pure Java embeddable LDAP v3 protocol daemon built on the Avalon framework. Alex donated the code to the Apache Software Foundation and the code entered the <a href="http://incubator.apache.org/">Apache Incubator</a> in October 2003. One year later in October of 2004, the Apache Directory Top Level Project (TLP) was formed after a successful incubation with the now called Apache Directory Server as its flagship product. After 4 years of development, in October 2006, Apache Directory Server 1.0 was released as an Open Group certified LDAPv3 protocol server. The certification has been renewed in September 2007.</p>
<p>Having a standards compliant and modern LDAP server, Apache Directory Team is now working on Identity and Access Management solutions leveraging the directory technology.</p>
-<h2 id="resources">Resources</h2>
+<h2 id="resources">Resources<a class="headerlink" href="#resources" title="Permanent link">¶</a></h2>
<ul>
<li><a href="../../original-project-proposal.html">Proposal for an Apache Directory Project</a> the original proposal for incubation, September 2003.</li>
<li><a href="../../vision.html">Architecting the Modern LDAP Renaissance: The Apache Directory Vision</a>, Paper for 1st International Conference on LDAP, September 2007.</li>
Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/1.2-some-background.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/1.2-some-background.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/1.2-some-background.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="12-some-background-directories-directory-services-and-ldap">1.2 - Some Background. Directories, directory services and LDAP</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="12-some-background-directories-directory-services-and-ldap">1.2 - Some Background. Directories, directory services and LDAP<a class="headerlink" href="#12-some-background-directories-directory-services-and-ldap" title="Permanent link">¶</a></h1>
<p>This section provides a brief overview about directories, directory services and LDAP. Furthermore you find links to different resources (books, online resources, ...), which may act as introduction to the topic. If you are already an LDAP expert, you'll probably skip this section. </p>
<div class="toc">
<ul>
@@ -199,23 +210,23 @@
</li>
</ul>
</div>
-<h2 id="directories-and-directory-services">Directories and directory services</h2>
+<h2 id="directories-and-directory-services">Directories and directory services<a class="headerlink" href="#directories-and-directory-services" title="Permanent link">¶</a></h2>
<p>Generally speaking, a directory is a collection or list of data. Real world examples are telephone books (public or within organizations), church/land registers and listings of works (e.g. the Koechel-index, which lists all compositions of Mozart). All these examples have the purpose to preserve information and to make it available on demand to whom it may concern.</p>
<p>Within information technology the term <em>directory</em> is used for a special kind of data storage. It allows the structured storage and efficient retrieval of objects which are often derived from the real world (e.g. persons, IT equipment). Characteristic:
<em> all data is stored in so called </em>entries<em>
</em> the set of entries within a directory forms a tree (hierarchical database)</p>
<p>A <em>directory service</em> is a solution which offers users access to the information stored in the directory. A directory assistance (call center agent) is a good real world example for such a service. Within information technologies, such services are normally provided by software components. Directory services provide access to the content of a directory via a well-defined interface. If a network is used, an appropriate protocol has to be defined. LDAP (see below) is such a protocol.</p>
<p>The real world examples mentioned above may be stored in such a directory, although other types of storage systems can be more appropriate (this depends on circumstance/requirements). At first sight directories compete thereby as data storage with the established relational data bases. However in the most large enterprises and organizations both directory services and relational databases are actually used. Read how Vikas Mahajan describes directories and databases as complementary, not competitive, solutions in his excellent article <a href="http://support.novell.com/techcenter/articles/ana20011101.html">"Should I Use a Directory, a Database, or Both?"</a>.</p>
-<h2 id="ldap-the-lightweight-directory-access-protocol">LDAP -- the Lightweight Directory Access Protocol</h2>
-<h3 id="what-is-it-some-history">What is it? Some history.</h3>
+<h2 id="ldap-the-lightweight-directory-access-protocol">LDAP -- the Lightweight Directory Access Protocol<a class="headerlink" href="#ldap-the-lightweight-directory-access-protocol" title="Permanent link">¶</a></h2>
+<h3 id="what-is-it-some-history">What is it? Some history.<a class="headerlink" href="#what-is-it-some-history" title="Permanent link">¶</a></h3>
<p>The comprehensive standard <em>X.500</em>, finalized in 1988, builds the foundation for many of today's directory solutions. Within this standard, the client accesses the server via the Directory Access Protocol (<em>DAP</em>), which is OSI protocol stack based. With the Internet boom in the nineties, the accessibility of directories via TCP/IP became more and more important. Hence a TCP/IP-based access method, which in functionality was a subset of DAP, was standardized in 1993: the <em>Lightweight Directory Access Protocol (LDAP)</em>. First LDAP implementations were gateway solutions, they mediated between LDAP clients and X.500 servers. In 1995 the University of Michigan presented the first native LDAP server; in the meantime the work is continued by the <a href="http://www.openldap.org/">OpenLDAP</a> project. 1996 Netscape followed with the first commercial LDAP server (Netscape Directory Server, foundation of several later LDAP servers). Other examples (among many others)
include <a href="http://www.microsoft.com/ad/">Microsoft Active Directory</a> and <a href="http://www.novell.com/products/edirectory/">Novell eDirectory</a>. The figure below shows the development of directory protocols from X.500/DAP to LDAP.</p>
<p><img alt="From X500 to LDAP" src="images/fromX500toLDAP.png" /></p>
-<h3 id="information-model-primer">Information model primer</h3>
+<h3 id="information-model-primer">Information model primer<a class="headerlink" href="#information-model-primer" title="Permanent link">¶</a></h3>
<p>Within the information model of LDAP, data is stored in entries, which build up a hierarchical, tree like structure. Each entry has a unique name (<em>DN</em>, <em>Distinguished Name</em>), which depicts its position within the tree. An entry consists of key/value pairs, the <em>attributes</em>. Some attributes may occur more than once within an entry (single or multi valued, e.g. a person can have more than one telephone number). So called <em>object classes</em> define, which attributes an entry may have, and which of them are required. The classes build up a hierarchy with <em>top</em> as root; there is a parallelism to the object oriented world. top forces only the attribute objectclass, which assigns an entry its object classes. A <em>schema</em> consists object classes and attribute types, and therefore defines, what kind of entries can be stored within the directory. Directory servers ship a schema out-of-the-box, often with elements standardized by RFCs. In addition, most
directory solutions allow you to define custom object classes and attributes. But in practice, the pre-defined elements are used. Sometimes they get extended according to special requirements.</p>
-<h3 id="common-applications-of-ldap-based-directories">Common applications of LDAP based directories</h3>
+<h3 id="common-applications-of-ldap-based-directories">Common applications of LDAP based directories<a class="headerlink" href="#common-applications-of-ldap-based-directories" title="Permanent link">¶</a></h3>
<p>LDAP operations include entry creation, modification, deletion and search. As a general rule, LDAP directories are optimized for read and search operations, at the cost of write performance. Data, which will be modified often, therefore better suits in a relational database, which offers better support for transactions and referential integrity as well. Directories are rather used if comparatively stable data has to be provided centrally.<br />
Common examples are network resources (printers, services) and user data (including credentials and rights for the resources). As a notable feature, many directory products offer replicas, which permit better access times and higher availability especially in geographically dispersed organizations. Not for nothing, the most common LDAP application is the enterprise phone book. That even Microsoft Outlook may be an LDAP client in this case - most average users probably don't know.</p>
-<h3 id="examples-of-software-components-which-support-ldap">Examples of software components which support LDAP</h3>
+<h3 id="examples-of-software-components-which-support-ldap">Examples of software components which support LDAP<a class="headerlink" href="#examples-of-software-components-which-support-ldap" title="Permanent link">¶</a></h3>
<p><img alt="LDAP tools" src="images/ldap-tools.png" /></p>
<p>Very different types of software products may act as LDAP clients, consuming data for authentication, authorization or data presentation etc.</p>
<ul>
@@ -226,29 +237,29 @@ Common examples are network resources (p
<li>...</li>
</ul>
<p>Configuration details for several of these programs in conjunction with ApacheDS are described in later sections.</p>
-<h2 id="ldap-resources">LDAP resources</h2>
-<h3 id="books">Books</h3>
+<h2 id="ldap-resources">LDAP resources<a class="headerlink" href="#ldap-resources" title="Permanent link">¶</a></h2>
+<h3 id="books">Books<a class="headerlink" href="#books" title="Permanent link">¶</a></h3>
<p>There are several good LDAP books available. Here are two examples which provide sample chapters on their homepages.</p>
-<h4 id="understanding-and-deploying-ldap-directory-services">Understanding and Deploying LDAP Directory Services</h4>
+<h4 id="understanding-and-deploying-ldap-directory-services">Understanding and Deploying LDAP Directory Services<a class="headerlink" href="#understanding-and-deploying-ldap-directory-services" title="Permanent link">¶</a></h4>
<p><img alt="cover" src="images/cover_howes_100.gif" /></p>
<p>Understanding and Deploying LDAP Directory Services (2nd Edition) <br/>
by Timothy A. Howes, Mark C. Smith, Gordon S. Good, Tim Howes <br/>
Addison-Wesley Professional, 2nd Edition 2003 <br/>
ISBN: 0-672323-16-8 <br/></p>
<p><a href="http://awprofessional.com/title/0672323168">Book's Homepage (Howes)</a></p>
-<h4 id="ldap-fuer-java-entwickler">LDAP fuer Java-Entwickler</h4>
+<h4 id="ldap-fuer-java-entwickler">LDAP fuer Java-Entwickler<a class="headerlink" href="#ldap-fuer-java-entwickler" title="Permanent link">¶</a></h4>
<p><img alt="cover" src="images/cover_zoerner_100.gif" /></p>
<p>LDAP fuer Java-Entwickler -- Einstieg und Integration. <img alt="DE" src="images/de.png" /> <br/>
von Stefan Zoerner <br/>
Software und Support Verlag, 3. aktualisierte Auflage 2007 <br/>
ISBN: 978-3-939084-07-5 <br/></p>
<p><a href="http://www.entwickler-press.de/buecher/ldap/">Webseite zum Buch (Zoerner)</a></p>
-<h3 id="articles-forums-blogs-and-other-online-resources">Articles, forums, blogs and other online resources</h3>
-<h4 id="blogs">Blogs</h4>
+<h3 id="articles-forums-blogs-and-other-online-resources">Articles, forums, blogs and other online resources<a class="headerlink" href="#articles-forums-blogs-and-other-online-resources" title="Permanent link">¶</a></h3>
+<h4 id="blogs">Blogs<a class="headerlink" href="#blogs" title="Permanent link">¶</a></h4>
<ul>
<li><a href="http://blogs.sun.com/roller/page/DirectoryManager">cn=Directory Manager - All about Directory Server</a>, Sun Blog</li>
</ul>
-<h4 id="articles-and-other-online-resources">Articles and other online resources</h4>
+<h4 id="articles-and-other-online-resources">Articles and other online resources<a class="headerlink" href="#articles-and-other-online-resources" title="Permanent link">¶</a></h4>
<ul>
<li><a href="http://www.redbooks.ibm.com/abstracts/SG244986.html?Open">Understanding LDAP - Design and Implementation</a>, IBM RedBook, July 2006</li>
<li><a href="http://www.oreillynet.com/pub/a/sysadmin/2006/07/27/demystifying-ldap.html">Demystifying LDAP</a> by Brian K. Jones, O'Reilly Network</li>
Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/1.3-installing-and-starting.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/1.3-installing-and-starting.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/1.3-installing-and-starting.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="13-installing-and-starting-the-server">1.3 - Installing and starting the server</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="13-installing-and-starting-the-server">1.3 - Installing and starting the server<a class="headerlink" href="#13-installing-and-starting-the-server" title="Permanent link">¶</a></h1>
<p>This section describes how ApacheDS can be installed and started on different platforms.</p>
<div class="toc">
<ul>
@@ -189,7 +200,7 @@
</li>
</ul>
</div>
-<h2 id="prerequisites">Prerequisites</h2>
+<h2 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">¶</a></h2>
<ul>
<li><strong>Java 7.0</strong>. We recommend using <a href="http://www.oracle.com/technetwork/java/javase/downloads/index.html">Oracle's JDK</a>.</li>
</ul>
@@ -208,7 +219,7 @@
<ul>
<li><strong>384 MB RAM</strong> for the JVM. That's the default setting, how to change that is described [here|1.4. Basic configuration tasks#MemoryAllocation]</li>
</ul>
-<h2 id="download-a-server-installer">Download a server installer</h2>
+<h2 id="download-a-server-installer">Download a server installer<a class="headerlink" href="#download-a-server-installer" title="Permanent link">¶</a></h2>
<p>We provide native installers for several platforms:</p>
<ul>
<li>Windows (exe)</li>
@@ -220,22 +231,22 @@
<p>Additional we provide an zip and tar.gz archive suitable for any platform.</p>
<p>You can download them from <a href="http://directory.apache.org/apacheds/downloads.html">here</a>.</p>
<p>An option for people familiar with tools like Subversion and Maven is to built the server from the sources on their own. This is described <a href="../advanced-ug/0.2-building-trunks.html">here</a>.</p>
-<h1 id="installation-on-windows">Installation on Windows</h1>
+<h1 id="installation-on-windows">Installation on Windows<a class="headerlink" href="#installation-on-windows" title="Permanent link">¶</a></h1>
<p>Installing can be easily done using the Windows installer. Its interface and functionality is similar to other wizard based installers.</p>
<p><CENTER>
<img alt="Windows Installer" src="images/Windows_Installer.png" />
</CENTER></p>
<p>To install the ApacheDS as Windows service you need <em>Administrator</em> privileges.</p>
-<h3 id="starting-and-stopping-the-server">Starting and stopping the server</h3>
+<h3 id="starting-and-stopping-the-server">Starting and stopping the server<a class="headerlink" href="#starting-and-stopping-the-server" title="Permanent link">¶</a></h3>
<p>The server can be started and stopped with Windows Services manager (<em>Control Panel > Administrative Tools > Services</em>). You must be admin to do this.</p>
<p>From there, you can easily start, stop and restart Apache DS.</p>
-<h2 id="installation-on-mac-os-x">Installation on Mac OS X</h2>
+<h2 id="installation-on-mac-os-x">Installation on Mac OS X<a class="headerlink" href="#installation-on-mac-os-x" title="Permanent link">¶</a></h2>
<p>To install Apache DS on Mac OS X, simply open the downloaded DMG file and then the "Apache Directory Server Installer.pkg" in it.</p>
<p><CENTER>
<img alt="MacOSX installer" src="images/MacOSX_Installer.png" />
</CENTER></p>
<p>From there, you will be guided to install Apache DS on your system.</p>
-<h3 id="starting-and-stopping-the-server_1">Starting and stopping the server</h3>
+<h3 id="starting-and-stopping-the-server_1">Starting and stopping the server<a class="headerlink" href="#starting-and-stopping-the-server_1" title="Permanent link">¶</a></h3>
<p>On Mac OS X, Apache DS is installed as a <a href="http://developer.apple.com/macosx/launchd.html">launchd</a> service and is loaded at startup time (and upon successful installation).</p>
<p>You can stop the server by unloading the launchd service with the following command line:</p>
<div class="codehilite"><pre><span class="n">sudo</span> <span class="n">launchctl</span> <span class="n">unload</span> <span class="o">/</span><span class="n">Library</span><span class="o">/</span><span class="n">LaunchDaemons</span><span class="o">/</span><span class="n">org</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">directory</span><span class="p">.</span><span class="n">server</span><span class="p">.</span><span class="n">plist</span>
@@ -263,7 +274,7 @@
<p>sudo launchctl start org.apache.directory.server</p>
<p>and stop it with :</p>
<p>sudo launchctl stop org.apache.directory.server</p>
-<h2 id="installation-on-linux">Installation on Linux</h2>
+<h2 id="installation-on-linux">Installation on Linux<a class="headerlink" href="#installation-on-linux" title="Permanent link">¶</a></h2>
<p>The installation for different installers is described on the <a href="http://directory.apache.org/apacheds/downloads.html">Apache Directory Server Downloads</a> page.</p>
Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/1.4-basic-configuration-tasks.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/1.4-basic-configuration-tasks.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/1.4-basic-configuration-tasks.html Sun Jul 5 22:34:35 2015
@@ -169,9 +169,20 @@
</div>
-<h1 id="14-basic-configuration-tasks">1.4 - Basic configuration tasks</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="14-basic-configuration-tasks">1.4 - Basic configuration tasks<a class="headerlink" href="#14-basic-configuration-tasks" title="Permanent link">¶</a></h1>
<p>In this chapter, we will explain how to configure some basic parameters in the server you just installed. We won't expose all the options in this <em>Basic User Guide</em>, you can check in the <em>Advanced User Guide</em> for more options if needed.</p>
-<h2 id="table-of-content">Table of content</h2>
+<h2 id="table-of-content">Table of content<a class="headerlink" href="#table-of-content" title="Permanent link">¶</a></h2>
<ul>
<li><a href="1.4.1-changing-server-port.html">1.4.1 - Changing the server port for LDAP</a></li>
<li><a href="1.4.2-changing-admin-password.html">1.4.2 - Changing the admin password</a></li>
Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.1-changing-server-port.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.1-changing-server-port.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.1-changing-server-port.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="141-changing-the-server-port-for-ldap">1.4.1 - Changing the server port for LDAP</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="141-changing-the-server-port-for-ldap">1.4.1 - Changing the server port for LDAP<a class="headerlink" href="#141-changing-the-server-port-for-ldap" title="Permanent link">¶</a></h1>
<p>This section describes how to change to port for the LDAP protocol. There are two ways to do that : either you use the configuration plugin available in <strong>Apache Directory Studio</strong>, or you update the LDIF partition that contains the configuration.</p>
<div class="toc">
<ul>
@@ -187,7 +198,7 @@
</li>
</ul>
</div>
-<h2 id="the-task-and-how-to-accomplish-it">The task and how to accomplish it</h2>
+<h2 id="the-task-and-how-to-accomplish-it">The task and how to accomplish it<a class="headerlink" href="#the-task-and-how-to-accomplish-it" title="Permanent link">¶</a></h2>
<p>By default the LDAP server listens on port 10389 (unencrypted or StartTLS) and 10636 (SSL). It is quite common to run LDAP on 389, which is the well-known port for this protocol, but that requires the server to be started with a root user (or with sudo). Of course other options are imaginable as well. Changing the LDAP port is a good example for adjusting the existing Spring configuration as introduced in the last section.</p>
<DIV class="note" markdown="1">
Due to traditional Unix security restrictions, ports less than 1024 were "trusted". Thus on a Unix-System, a non-root process must listen on a port greater than 1023.
@@ -197,8 +208,8 @@ Due to traditional Unix security restric
<em> The server is not started
</em> The server is started</p>
<p>We will see how to change the port in those two cases.</p>
-<h3 id="using-apache-directory-studio">Using Apache Directory Studio</h3>
-<h4 id="the-server-is-started">The server is started</h4>
+<h3 id="using-apache-directory-studio">Using Apache Directory Studio<a class="headerlink" href="#using-apache-directory-studio" title="Permanent link">¶</a></h3>
+<h4 id="the-server-is-started">The server is started<a class="headerlink" href="#the-server-is-started" title="Permanent link">¶</a></h4>
<p>The best solution is to connect on the server using Studio, and to open it's configuration :</p>
<p><CENTER>
<img alt="Studio port configuration" src="images/studio-port-config1.png" />
@@ -208,7 +219,7 @@ Due to traditional Unix security restric
<img alt="Studio port configuration" src="images/studio-port-config2.png" />
</CENTER></p>
<p>Now, change the values of <em>port</em> to your needs, then save the configuration. You have to restart the server afterwards in order to take this change into effect.</p>
-<h4 id="the-server-is-not-started">The server is not started</h4>
+<h4 id="the-server-is-not-started">The server is not started<a class="headerlink" href="#the-server-is-not-started" title="Permanent link">¶</a></h4>
<p>You can start it and update the configuration, of course. But if you want to configure the server when it's stopped, you will have to load the configuration file, which is on <em>.../instances/default/conf/config.ldif</em>, when the server has been installed using the default setting.</p>
<p>Opening this file will open the exact same window :</p>
<p><CENTER>
@@ -219,7 +230,7 @@ Due to traditional Unix security restric
Note that you will requite write access on this file !
</DIV>
-<h3 id="modifying-the-configuration-ldif-partition">Modifying the configuration LDIF partition</h3>
+<h3 id="modifying-the-configuration-ldif-partition">Modifying the configuration LDIF partition<a class="headerlink" href="#modifying-the-configuration-ldif-partition" title="Permanent link">¶</a></h3>
<p>All the <strong>ApacheDS</strong> configuration is stored as a LDIF file, and can be modified either using a text editor (although we don't consider this as a safe practice) or using a Modify request on a running server. </p>
<DIV class="info" markdown="1">
Modifying the configuration on a running server will **not** change the listening port of the running server. You will have to relaunch the server in order to get this new configuration to be available.
Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.2-changing-admin-password.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.2-changing-admin-password.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.2-changing-admin-password.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="142-changing-the-admin-password">1.4.2 - Changing the admin password</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="142-changing-the-admin-password">1.4.2 - Changing the admin password<a class="headerlink" href="#142-changing-the-admin-password" title="Permanent link">¶</a></h1>
<p>This section describes the steps necessary to change the administrator password. Follow the instructions provided here step by step.</p>
<div class="toc">
<ul>
@@ -181,7 +192,7 @@
</li>
</ul>
</div>
-<h2 id="step-one-changing-the-value-in-the-system-partition">Step one: Changing the value in the system partition</h2>
+<h2 id="step-one-changing-the-value-in-the-system-partition">Step one: Changing the value in the system partition<a class="headerlink" href="#step-one-changing-the-value-in-the-system-partition" title="Permanent link">¶</a></h2>
<p>While the server is up and running, change the value of the <em>userPassword</em> attribute of the admin (uid=admin,ou=system) via LDAP. There are several ways to accomplish this task. In the following, we use the Eclipse based Apache Directory Studio.</p>
<p>A new LDAP connection with this tool is created via "New Connection ..." from the <em>Connections</em> view. Enter your connection data in the first step ...</p>
<p><img alt="New LDAP connection" src="images/NewLDAPConnection1.png" /></p>
@@ -193,11 +204,11 @@
<p>The Password Editor dialog shows up; enter the new password. You can optionally select a hash algorithm like <em>SHA</em>. In this case, the password will be stored one-way encrypted in the attribute value -- not a bad idea.</p>
<p><img alt="Password Editor" src="images/passwordEditor.png" /></p>
<p>Pressing <em>OK</em> stores the new value. Close the connection and shutdown the server.</p>
-<h2 id="step-two-verification">Step two: Verification</h2>
+<h2 id="step-two-verification">Step two: Verification<a class="headerlink" href="#step-two-verification" title="Permanent link">¶</a></h2>
<p>Verify that you can login as admin with the new password. With Apache Directory Studio, you can change the properties of the existing connection profile via a right click in the <em>Connections</em> view and a selection of the <em>Properties</em> menu item. The following dialog appears:</p>
<p><img alt="Connection Properties" src="images/connectionProperties.png" /></p>
<p>Enter the new password and press <em>OK</em>. Establishing a connection should now work. </p>
-<h2 id="resources">Resources</h2>
+<h2 id="resources">Resources<a class="headerlink" href="#resources" title="Permanent link">¶</a></h2>
<ul>
<li><a href="http://directory.apache.org/studio/">Apache Directory Studio</a>: The tool used in steps 1 and 2</li>
</ul>
Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.3-adding-partition.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.3-adding-partition.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.3-adding-partition.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="143-adding-your-own-partition-resp-suffix">1.4.3 - Adding your own partition resp. suffix</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="143-adding-your-own-partition-resp-suffix">1.4.3 - Adding your own partition resp. suffix<a class="headerlink" href="#143-adding-your-own-partition-resp-suffix" title="Permanent link">¶</a></h1>
<p>This section describes how to add your own data partition.</p>
<div class="toc">
<ul>
@@ -182,12 +193,12 @@
</li>
</ul>
</div>
-<h2 id="what-are-partitions">What are partitions?</h2>
+<h2 id="what-are-partitions">What are partitions?<a class="headerlink" href="#what-are-partitions" title="Permanent link">¶</a></h2>
<p>In ApacheDS entries are stored in partitions. Each partition contains a complete entry tree, also referred to as a DIT. Multiple partitions may exist and the entry trees they contain are disconnected from each other, meaning that changes to entries in partition <em>A</em> would never affect entries in partition <em>B</em>. The entries in a particular partition are stored below some naming context called the partition suffix.</p>
<p>The default implementation of partitions is based on <a href="http://jdbm.sourceforge.net/">JDBM</a> B+Trees (but it's possible to add custom partition implementations). The ApacheDS default configuration contains a a data partition with the suffix "dc=example,dc=com". The image below shows the suffixes of a freshly installed ApacheDS within Apache Directory Studio.</p>
<p><img alt="Partition in studio after installation" src="images/partitions-in-studio-after-installation.png" /></p>
<p>The schema subsystem and ApacheDS itself store their information in special partitions, "ou=schema", "ou=config" and "ou=system" respectively.</p>
-<h2 id="minimal-partition-definition">Minimal partition definition</h2>
+<h2 id="minimal-partition-definition">Minimal partition definition<a class="headerlink" href="#minimal-partition-definition" title="Permanent link">¶</a></h2>
<p>For the examples in the following sections, we want to add a partition with the suffix "o=sevenSeas". This requires editing of the configuration, and injecting a first entry, associated with the root of this partition (here, "o=sevenseas"). This can be done using <em>Apache Directory Studio</em>. Open the server configuration :</p>
<p><img alt="Studio Apacheds Configuration" src="images/studio-apacheds-configuration1.png" /></p>
<p>and select the <em>Partitions</em> tab :</p>
@@ -211,7 +222,7 @@
<p>In the LDAP Browser of Directory Studio, right click on the DIT entry and select "Import -> LDIF Import...". A file selections dialog appears. Browse to the LDIF file and click Finish. The entry (or entries, if you provide more of them) will be added to to partition.</p>
<p>The following image depicts the partitions after reconnecting with Apache Directory Studio (<em>LDAP Browser</em> view).</p>
<p><img alt="Partition in Studio after addition" src="images/partitions-in-studio-after-addition.png" /></p>
-<h2 id="adding-a-partition-programmatically">Adding a partition programmatically</h2>
+<h2 id="adding-a-partition-programmatically">Adding a partition programmatically<a class="headerlink" href="#adding-a-partition-programmatically" title="Permanent link">¶</a></h2>
<p>The same o=sevenseas partition can be created through the application code using the Partition and DirectoryService API</p>
<p>Here is the sample code to create a new partition o=sevenseas and its context entry programmatically</p>
<div class="codehilite"><pre><span class="c1">// Get the SchemaManager, we need it for this addition</span>
@@ -246,7 +257,7 @@
</pre></div>
-<h2 id="more-configuration-options-for-a-jdbm-partition">More configuration options for a JDBM partition</h2>
+<h2 id="more-configuration-options-for-a-jdbm-partition">More configuration options for a JDBM partition<a class="headerlink" href="#more-configuration-options-for-a-jdbm-partition" title="Permanent link">¶</a></h2>
<p>Here is a list of the used attributes, their default values and meaning :</p>
<table>
<thead>
Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.4-configure-logging.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.4-configure-logging.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.4-configure-logging.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="144-configure-logging">1.4.4 - Configure logging</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="144-configure-logging">1.4.4 - Configure logging<a class="headerlink" href="#144-configure-logging" title="Permanent link">¶</a></h1>
<p>In order to detect and analyze problems, adjusting the log level of a server can be a valuable tool. This section describes how to configure logging within a standalone ApacheDS. </p>
<div class="toc">
<ul>
@@ -194,9 +205,9 @@
</li>
</ul>
</div>
-<h2 id="apacheds-and-logging">ApacheDS and logging</h2>
+<h2 id="apacheds-and-logging">ApacheDS and logging<a class="headerlink" href="#apacheds-and-logging" title="Permanent link">¶</a></h2>
<p>ApacheDS 2.0 uses <a href="http://www.slf4j.org/">SLF4J</a> as its logging solution. This is a simple facade for various logging APIs. The default for ApacheDS 2.0 is <a href="http://logging.apache.org/log4j/">log4j</a>.</p>
-<h2 id="default-behavior-after-installation">Default behavior after installation</h2>
+<h2 id="default-behavior-after-installation">Default behavior after installation<a class="headerlink" href="#default-behavior-after-installation" title="Permanent link">¶</a></h2>
<p>By default, ApacheDS writes log files in the directory <em><APACHEDS_HOME>/var/log/</em>. Besides stdout, a <a href="http://logging.apache.org/log4j/docs/api/org/apache/log4j/RollingFileAppender.html">RollingFileAppender</a> is used to collect warnings and errors. It backups the log files when they reach a certain size. </p>
<p>Here is what the default configuration file <em>log4j.properties</em>, which is located in <em><APACHEDS_HOME>/conf/</em>, looks like.
The name of the <em>RollingFileAppender</em> is "R":</p>
@@ -252,16 +263,16 @@ The name of the <em>RollingFileAppender<
</tr>
<tr>
<td align="center">layout.ConversionPattern</td>
-<td align="center">[%d{HH:mm:ss}] %p [%c] - %m%n</td>
+<td HH:mm:ss="HH:mm:ss" align="center">[%d</td>
<td>Format string for logging events</td>
</tr>
</tbody>
</table>
<p>If the default logging does not meet your requirements, you can easily adjust the configuration to your needs.</p>
-<h2 id="adjusting-logging-to-your-needs">Adjusting logging to your needs</h2>
-<h3 id="log-file-location-where-the-log-files-are-placed">Log file location (where the log files are placed)</h3>
+<h2 id="adjusting-logging-to-your-needs">Adjusting logging to your needs<a class="headerlink" href="#adjusting-logging-to-your-needs" title="Permanent link">¶</a></h2>
+<h3 id="log-file-location-where-the-log-files-are-placed">Log file location (where the log files are placed)<a class="headerlink" href="#log-file-location-where-the-log-files-are-placed" title="Permanent link">¶</a></h3>
<p>By default the log files are placed at <em><APACHEDS_HOME>/var/log/</em>, but that can be changed.</p>
-<h4 id="linuxmacossolaris">Linux/MacOS/Solaris</h4>
+<h4 id="linuxmacossolaris">Linux/MacOS/Solaris<a class="headerlink" href="#linuxmacossolaris" title="Permanent link">¶</a></h4>
<p>On this systems the location of the log files is configured via an entry in <em>/bin/server.init</em>. Look for the following lines and change it to your preferences:</p>
<div class="codehilite"><pre>$<span class="n">DAEMON_HOME</span><span class="o">/</span><span class="n">apacheds</span> <span class="o">\</span>
<span class="p">...</span>
@@ -272,9 +283,9 @@ $<span class="n">APACHEDS_HOME</span> <s
</pre></div>
-<h4 id="windows">Windows</h4>
+<h4 id="windows">Windows<a class="headerlink" href="#windows" title="Permanent link">¶</a></h4>
<p>On Windows you can use the configuration wizard for the service as shown in the screenshot above. To adjust the log path you have to adjust the values of <em>Redirect Stdout</em> and <em>Redirect Stderror</em></p>
-<h3 id="log-level-how-detailed-the-logs-are">Log level (how detailed the logs are)</h3>
+<h3 id="log-level-how-detailed-the-logs-are">Log level (how detailed the logs are)<a class="headerlink" href="#log-level-how-detailed-the-logs-are" title="Permanent link">¶</a></h3>
<p>The following log levels from log4j are used for messages within ApacheDS:</p>
<table>
<thead>
@@ -324,7 +335,7 @@ $<span class="n">APACHEDS_HOME</span> <s
<p>If the global level is switched to DEBUG, these definitions override the setting with WARN for certain areas and therefore keep the file a little bit smaller. Learn more about the concept of categories in the <a href="http://logging.apache.org/log4j/docs/manual.html">Short introduction to log4j</a>. </p>
-<h3 id="format-for-log-messages">Format for log messages</h3>
+<h3 id="format-for-log-messages">Format for log messages<a class="headerlink" href="#format-for-log-messages" title="Permanent link">¶</a></h3>
<p>The format of each line within a log file is controlled by a pattern. For the <em>RollingFileAppender</em> in the default configuration it looks like this</p>
<div class="codehilite"><pre><span class="p">...</span>
<span class="n">log4j</span><span class="p">.</span><span class="n">appender</span><span class="p">.</span><span class="n">R</span><span class="p">.</span><span class="n">layout</span><span class="p">=</span><span class="n">org</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">log4j</span><span class="p">.</span><span class="n">PatternLayout</span>
@@ -357,7 +368,7 @@ $<span class="n">APACHEDS_HOME</span> <s
<tbody>
<tr>
<td align="center">%d</td>
-<td>Date of the logging event in the given format. like "12:29:05" for %d{HH:mm:ss}</td>
+<td HH:mm:ss="HH:mm:ss">Date of the logging event in the given format. like "12:29:05" for %d</td>
</tr>
<tr>
<td align="center">%p</td>
@@ -398,10 +409,10 @@ $<span class="n">APACHEDS_HOME</span> <s
"Generating caller location information like with %M or %L is extremely slow. Its use should be avoided unless execution speed is not an issue." (from the log4j documentation)
</DIV>
-<h3 id="advanced-log4j-configuration">Advanced log4j configuration</h3>
+<h3 id="advanced-log4j-configuration">Advanced log4j configuration<a class="headerlink" href="#advanced-log4j-configuration" title="Permanent link">¶</a></h3>
<p>You can take advantage of other features of log4j as well, such as other appenders like the daily rolling file appender. And you can configure logging to make it easier for you to view the messages with tools like Log Factor 5 or <a href="http://logging.apache.org/log4j/docs/chainsaw.html">Chainsaw</a>.</p>
<p>Learn more about log4j and related tools at its <a href="http://logging.apache.org/log4j/docs/index.html">homepage</a>.</p>
-<h2 id="example-configurations">Example configurations</h2>
+<h2 id="example-configurations">Example configurations<a class="headerlink" href="#example-configurations" title="Permanent link">¶</a></h2>
<p>The following example could be used to log all incoming search, add, delete, modify and moddn requests:</p>
<div class="codehilite"><pre><span class="n">log4j</span><span class="p">.</span><span class="n">logger</span><span class="p">.</span><span class="n">org</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">directory</span><span class="p">.</span><span class="n">server</span><span class="p">.</span><span class="n">ldap</span><span class="p">.</span><span class="n">handlers</span><span class="p">.</span><span class="n">SearchHandler</span><span class="p">=</span><span class="n">DEBUG</span>
<span class="n">log4j</span><span class="p">.</span><span class="n">logger</span><span class="p">.</span><span class="n">org</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">directory</span><span class="p">.</span><span class="n">server</span><span class="p">.</span><span class="n">ldap</span><span class="p">.</span><span class="n">handlers</span><span class="p">.</span><span class="n">AddHandler</span><span class="p">=</span><span class="n">DEBUG</span>
@@ -411,11 +422,11 @@ $<span class="n">APACHEDS_HOME</span> <s
</pre></div>
-<h2 id="log-settings-of-the-windows-daemon-process">Log settings of the Windows daemon process</h2>
+<h2 id="log-settings-of-the-windows-daemon-process">Log settings of the Windows daemon process<a class="headerlink" href="#log-settings-of-the-windows-daemon-process" title="Permanent link">¶</a></h2>
<p>After installation on Windows, you have the option to configure the ApacheDS Windows Service (you can do this later as well). If you do so, one option pane is dedicated to logging:</p>
<p><img alt="Windows service properties" src="images/w32_service_properties.png" /></p>
<p>You can adjust the logging level and a log path. Note that this is for the daemon only. The server itself is configured as described above.</p>
-<h2 id="resources">Resources</h2>
+<h2 id="resources">Resources<a class="headerlink" href="#resources" title="Permanent link">¶</a></h2>
<ul>
<li><a href="http://logging.apache.org/log4j/docs/manual.html">Short introduction to log4j</a></li>
</ul>
Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.5-anonymous-access.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.5-anonymous-access.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.5-anonymous-access.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="145-enable-and-disable-anonymous-access">1.4.5 - Enable and disable anonymous access</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="145-enable-and-disable-anonymous-access">1.4.5 - Enable and disable anonymous access<a class="headerlink" href="#145-enable-and-disable-anonymous-access" title="Permanent link">¶</a></h1>
<p>This section briefly describes how to enable and disable anonymous access.</p>
<p>Anonymous access to the server is enabled by default. This includes read and write access! </p>
<p>You can disable anonymous binds by changing the value for property <em>allow Anonymous Access</em> in the server configuration screen :</p>
Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/1.5-sample-configuration.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/1.5-sample-configuration.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/1.5-sample-configuration.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="15-about-the-sample-configurations-and-sample-directory-data">1.5. - About the sample configurations and sample directory data</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="15-about-the-sample-configurations-and-sample-directory-data">1.5. - About the sample configurations and sample directory data<a class="headerlink" href="#15-about-the-sample-configurations-and-sample-directory-data" title="Permanent link">¶</a></h1>
<p>This section describes basic parameters used throughout the examples in this guide. It also introduces the sample directory "Sailors of the seven seas", and other requisites you need.</p>
<div class="toc">
<ul>
@@ -181,7 +192,7 @@
</li>
</ul>
</div>
-<h2 id="basic-server-parameters">Basic server parameters</h2>
+<h2 id="basic-server-parameters">Basic server parameters<a class="headerlink" href="#basic-server-parameters" title="Permanent link">¶</a></h2>
<p>In the following sections we assume that you will install, configure and run Apache Directory Server on a host with the following host name using the parameters given in the following table:</p>
<table>
<thead>
@@ -215,12 +226,12 @@
</table>
<p>Before you start playing with the data make sure that you have added a partition with the suffix o=sevenSeas to the server. How to do this is described [here|1.4. Basic configuration tasks#Adding your own partition (suffix)]
In order to increase recognition, all examples of the Basic User's Guide use these values. Adjust them to your needs (especially the password).</p>
-<h2 id="ldap-clients">LDAP Clients</h2>
+<h2 id="ldap-clients">LDAP Clients<a class="headerlink" href="#ldap-clients" title="Permanent link">¶</a></h2>
<p>LDAP is a client/server protocol. Hence you need an LDAP client to connect remotely to the Apache Directory Server (or at least the directory part of it, to be precise). There are different options here. Because the protocol is standardized, you may use every LDAP compliant client. This is comparable to HTTP, where you can use each web browser to communicate with virtually each web server, and totally different to relational databases. The latter have a (more or less) standardized query language (SQL), but vendors tend to use individual network access protocols. In practice, the LDAP situation is even better than HTTP, because there were no LDAP browser wars ...</p>
<p>Many software components may act as an LDAP client. Normally they use LDAP libraries to connect. In the following sections you meet LDAP clients with GUI and LDAP command line tools. Some Java programming examples which takes advantage of JNDI are provided as well.</p>
<p>In other sections you will learn how E-Mail clients like Mozilla Thunderbird and application servers like Apache Tomcat connect to Apache Directory server, either to use the data stored in the directory (e.g. mail addresses) or to perform authentication and authorization.</p>
<p>Recapitulating the Basic User's Guide describes connecting to the server with tools provided by ApacheDS as well as third party products. In all cases the examples will use the connection data depicted above (<em>ldap://zanzibar:10389/o=sevenSeas</em>)</p>
-<h2 id="the-sample-data-sailors-of-the-seven-seas">The sample data (Sailors of the seven seas)</h2>
+<h2 id="the-sample-data-sailors-of-the-seven-seas">The sample data (Sailors of the seven seas)<a class="headerlink" href="#the-sample-data-sailors-of-the-seven-seas" title="Permanent link">¶</a></h2>
<p>The file <a href="resources/apache-ds-tutorial.ldif">Apache DS Tutorial</a> contains some sample data, which is used in the following sections. It is a text file in the so called <em>LDIF</em> format. LDIF stands for LDAP Data Interchange Format. It is widely adopted in the LDAP world and standardized in <a href="http://www.faqs.org/rfcs/rfc2849.html">RFC 2849</a>. Therefore you are able to import our sample data into other directory solutions as well, not only into Apache Directory Server.</p>
<p>The sample directory tree contains entries for persons and groups. These are structured in sub trees (ou=people and ou=groups), see image below. The person entries describe sailors (historic and fictional), the group entries bundle them. An example for a group is the ship crew of HMS Bounty.</p>
<p><img alt="Sample Structure" src="images/sample-structure.gif" /></p>
Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/2-handling-data.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/2-handling-data.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/2-handling-data.html Sun Jul 5 22:34:35 2015
@@ -169,9 +169,20 @@
</div>
-<h1 id="2-handling-data-within-your-directory">2 - Handling data within your directory</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="2-handling-data-within-your-directory">2 - Handling data within your directory<a class="headerlink" href="#2-handling-data-within-your-directory" title="Permanent link">¶</a></h1>
<p>Now that your server is up and running, you can use it to add, modify, remove and search entries. You can also manage its schema, extending it to fit your needs.</p>
-<h2 id="table-of-content">Table of content</h2>
+<h2 id="table-of-content">Table of content<a class="headerlink" href="#table-of-content" title="Permanent link">¶</a></h2>
<ul>
<li><a href="2.1-data-modification.html">2.1 - Data modification</a><ul>
<li><a href="2.1.1-adding-entries.html">2.1.1 - Adding Entries</a></li>
Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/2.1-data-modification.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/2.1-data-modification.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/2.1-data-modification.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="21-data-modification">2.1 - Data modification</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="21-data-modification">2.1 - Data modification<a class="headerlink" href="#21-data-modification" title="Permanent link">¶</a></h1>
<p>We will first expose the way you inject entries in <em>Apache Directory Server</em>. There are four type of operations you can use for that :
<em> Addition
</em> Deletion
@@ -178,7 +189,7 @@
<p>(The last operation allows a user to move, rename or move and rename entries).</p>
<p>We will show how to add or delete entries in the following chapters, just to show you how it works with <em>Apache Directory Server</em>. There is nothing really different with any other servers.</p>
<p>For further information about data modifications, you should either check the <a href="../../api/index.html">Apache LDAP API documentation</a> documentation, or the <a href="../../studio/users-guide.html">Apache Directory Studio documentation</a>.</p>
-<h2 id="table-of-content">Table of content</h2>
+<h2 id="table-of-content">Table of content<a class="headerlink" href="#table-of-content" title="Permanent link">¶</a></h2>
<ul>
<li><a href="2.1.1-adding-entries.html">2.1.1 - Adding Entries</a></li>
<li><a href="2.1.2-deleting-entries.html">2.1.2 - Deleting Entries</a></li>
Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/2.1.1-adding-entries.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/2.1.1-adding-entries.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/2.1.1-adding-entries.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="211-adding-entries">2.1.1 - Adding Entries</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="211-adding-entries">2.1.1 - Adding Entries<a class="headerlink" href="#211-adding-entries" title="Permanent link">¶</a></h1>
<p>We will see how to add new entries into the server. Assuming that we have already created a partition (see <a href="1.4.3-adding-partition.html">Adding a partition</a>), we will use this added partition as a root for the entry addition. We will also create the <em>ou=people</em> entry.</p>
<p>We try to add a new user to the "Seven Seas" partition. The data for the entry is inspired by "Peter Pan" and provided by this LDIF file (<a href="resources/captain-hook-hierarchy.ldif">Captain hook</a>): </p>
<div class="codehilite"><pre><span class="c"># File captain_hook.ldif</span>
@@ -192,7 +203,7 @@
<p>The first entry creates the <em>ou=people</em> container, which is necessary otherwise we can't inject the second entry.</p>
-<h2 id="using-the-command-line">Using the command line</h2>
+<h2 id="using-the-command-line">Using the command line<a class="headerlink" href="#using-the-command-line" title="Permanent link">¶</a></h2>
<p>You have to use an authorized user to inject the entry, here, <em>cn=Horatio Nelson,ou=people,o=sevenSeas</em> :</p>
<div class="codehilite"><pre>$ <span class="n">ldapmodify</span> <span class="o">-</span><span class="n">h</span> <span class="n">zanzibar</span> <span class="o">-</span><span class="n">p</span> 10389 <span class="o">-</span><span class="n">D</span> "<span class="n">cn</span><span class="p">=</span><span class="n">Horatio</span> <span class="n">Nelson</span><span class="p">,</span><span class="n">ou</span><span class="p">=</span><span class="n">people</span><span class="p">,</span><span class="n">o</span><span class="p">=</span><span class="n">sevenSeas</span>" <span class="o">-</span><span class="n">w</span> <span class="n">pass</span> <span class="o">\\</span>
<span class="o">-</span><span class="n">a</span> <span class="o">-</span><span class="n">f</span> <span class="n">captain_hook</span><span class="p">.</span><span class="n">ldif</span>
@@ -211,7 +222,7 @@ $
</pre></div>
-<h2 id="using-apache-directory-studio">Using Apache Directory Studio</h2>
+<h2 id="using-apache-directory-studio">Using Apache Directory Studio<a class="headerlink" href="#using-apache-directory-studio" title="Permanent link">¶</a></h2>
<p>Once connected on the server with studio, you should be able to inject new entries -assuming you have the sufficent priviledge - :</p>
<p><img alt="Import entry with studio" src="images/import-entry-studio.png" /></p>
<p>Then select the LDIF file containing the entry :</p>
Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/2.1.2-deleting-entries.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/2.1.2-deleting-entries.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/2.1.2-deleting-entries.html Sun Jul 5 22:34:35 2015
@@ -169,13 +169,24 @@
</div>
-<h1 id="212-deleting-entries">2.1.2 - Deleting Entries</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="212-deleting-entries">2.1.2 - Deleting Entries<a class="headerlink" href="#212-deleting-entries" title="Permanent link">¶</a></h1>
<p>Deleting entries is quite simple : you just need to provide their <em>DN</em>, and require for the deletion of the associated entry. Although there are a few conditions that must be fulfilled for this operatio to be successful :
<em> The entry must exist;
</em> It should not have any children;
* The user requiring the deletion must have enough priviledge to do so</p>
<p>Assuming those three conditions being fulfilled, you can proceed with the deletion. We will show how it works on the entry we added in the previous chapter.</p>
-<h2 id="using-the-command-line">Using the command line</h2>
+<h2 id="using-the-command-line">Using the command line<a class="headerlink" href="#using-the-command-line" title="Permanent link">¶</a></h2>
<p>You have to use an authorized user to delete the entry, here, <em>cn=Horatio Nelson,ou=people,o=sevenSeas</em> :</p>
<p>With an LDIF file (<a href="resources/captain-hook-delete.ldif">Captain hook delete</a>) with an appropriate change entry, this can easily be accomplished, if the bind user is allowed to do so. Here is the content of this <em>LDIF</em> file :</p>
<div class="codehilite"><pre><span class="c"># File captain_hook_delete.ldif</span>
@@ -192,7 +203,7 @@ $
</pre></div>
-<h2 id="using-apache-directory-studio">Using Apache Directory Studio</h2>
+<h2 id="using-apache-directory-studio">Using Apache Directory Studio<a class="headerlink" href="#using-apache-directory-studio" title="Permanent link">¶</a></h2>
<p>With studio, just select the entry you want to delete, and select the "Delete" menu :</p>
<p><img alt="Delete entry with studio" src="images/delete-entry.png" /></p>
<p>When deleteed, the <em>log</em> windows should contain this message :</p>
Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/2.2-searching-data.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/2.2-searching-data.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/2.2-searching-data.html Sun Jul 5 22:34:35 2015
@@ -169,10 +169,21 @@
</div>
-<h1 id="22-searching-data">2.2 - Searching Data</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="22-searching-data">2.2 - Searching Data<a class="headerlink" href="#22-searching-data" title="Permanent link">¶</a></h1>
<p>Searching is the most frequent operation done on a LDAP server : everything is optimized so that the search operation is as fast as possible.</p>
<p>We will show how to do some simple searches on <em>Apache Directory Server</em> in the following pages.</p>
-<h2 id="table-of-content">Table of content</h2>
+<h2 id="table-of-content">Table of content<a class="headerlink" href="#table-of-content" title="Permanent link">¶</a></h2>
<ul>
<li><a href="2.2.1-simple-search.html">2.2.1 - Simple search</a></li>
<li><a href="2.2.2-more-search-options.html">2.2.2 - More search options</a></li>
Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/2.2.1-simple-search.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/2.2.1-simple-search.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/2.2.1-simple-search.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="221-simple-search">2.2.1 - Simple search</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="221-simple-search">2.2.1 - Simple search<a class="headerlink" href="#221-simple-search" title="Permanent link">¶</a></h1>
<p>Basically, a search in <strong>LDAP</strong> requires a few parameters :
<em> A server on which we will send the request
</em> A port for this server
@@ -179,7 +190,7 @@
<em> A scope, defining the depth we should look for
</em> The list of attributes to return</p>
<p>There are several other options, which will be exposed in the next chapter.</p>
-<h2 id="doing-a-simple-search-on-the-command-line">Doing a Simple Search on the command line</h2>
+<h2 id="doing-a-simple-search-on-the-command-line">Doing a Simple Search on the command line<a class="headerlink" href="#doing-a-simple-search-on-the-command-line" title="Permanent link">¶</a></h2>
<p>Here is an exemple of search done on the base we have created :</p>
<div class="codehilite"><pre>$ <span class="n">ldapsearch</span> <span class="o">-</span><span class="n">h</span> <span class="n">zanzibar</span> <span class="o">-</span><span class="n">p</span> 10389 <span class="o">-</span><span class="n">b</span> "<span class="n">o</span><span class="p">=</span><span class="n">sevenSeas</span>" <span class="o">-</span><span class="n">s</span> <span class="n">sub</span> "<span class="p">(</span><span class="n">cn</span><span class="p">=</span><span class="n">James</span> <span class="n">Hook</span><span class="p">)</span>" <span class="o">+</span>
<span class="n">version</span><span class="p">:</span> 1
Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/2.2.2-more-search-options.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/2.2.2-more-search-options.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/2.2.2-more-search-options.html Sun Jul 5 22:34:35 2015
@@ -169,13 +169,24 @@
</div>
-<h1 id="222-more-search-options">2.2.2 - More search options</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="222-more-search-options">2.2.2 - More search options<a class="headerlink" href="#222-more-search-options" title="Permanent link">¶</a></h1>
<p>There are many parameters we haven't explained in the previous chapter. </p>
-<h2 id="boundanonymous-searches">Bound/anonymous searches</h2>
+<h2 id="boundanonymous-searches">Bound/anonymous searches<a class="headerlink" href="#boundanonymous-searches" title="Permanent link">¶</a></h2>
<p>When you send a SearchRequest to the server, you may be anonymous, or you may have been bound before the search is done. Binding on a server creates an <strong>LDAP</strong> session, which stores the credentials. This is used by the authorization system to filter the requests and the returned data, depending on the server settings.</p>
<p>Not all the server allow an anonymous search : <em>Apache Directory Server</em> default to not enabling such anonymous searches (this is for security questions).</p>
<p>Generally speaking, users do bind before sending a search request.</p>
-<h2 id="filters">Filters</h2>
+<h2 id="filters">Filters<a class="headerlink" href="#filters" title="Permanent link">¶</a></h2>
<p>The <strong>LDAP</strong> filters can be quite complex. Although they aren't even close to what <strong>SQL</strong> provide : there is no way you can do a Join on a LDAP server.</p>
<p>A filter is a set of nodes connected with operators like <strong>and</strong>, <strong>or</strong>, <strong>not</strong>...</p>
<p>Here is the list of possible connectors :</p>
@@ -236,14 +247,14 @@
</tr>
</tbody>
</table>
-<h2 id="scope">Scope</h2>
+<h2 id="scope">Scope<a class="headerlink" href="#scope" title="Permanent link">¶</a></h2>
<p>A Search can span across the whole <strong>DIT</strong>, or just a subset of it. In <strong>LDAP</strong>, you can use three different scopes :</p>
<ul>
<li>OBJECT : the Object itself, none of its children</li>
<li>ONELEVEL : all of the base direct children, but not it's children's children not the base object</li>
<li>SUBLEVEL : everything</li>
</ul>
-<h2 id="returned-attributes">Returned attributes</h2>
+<h2 id="returned-attributes">Returned attributes<a class="headerlink" href="#returned-attributes" title="Permanent link">¶</a></h2>
<p>A search can also list the attributes to be returned. This can be :
<em> '</em>' for all the user attributes
<em> '+' for all the operational attributes
Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/2.3-introducing-schema.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/2.3-introducing-schema.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/2.3-introducing-schema.html Sun Jul 5 22:34:35 2015
@@ -169,14 +169,25 @@
</div>
-<h1 id="23-the-schema">2.3 - The Schema</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="23-the-schema">2.3 - The Schema<a class="headerlink" href="#23-the-schema" title="Permanent link">¶</a></h1>
<p>All the data stored into a LDAP server are structured following a schema, a bit like any DBMS. <em>Apache Directory Server</em> does have a dynamic schema : that means you can modify the schema without having to restart the server.</p>
<p>We won't describe in the basic user guide how to manage the schema, this will be extensively described in the <em>Advanced user guide</em>, this chapter is just a short introduction.</p>
-<h2 id="table-of-content">Table of content</h2>
+<h2 id="table-of-content">Table of content<a class="headerlink" href="#table-of-content" title="Permanent link">¶</a></h2>
<ul>
<li><a href="2.3.1-adding-schema-elements.html">2.3.1 - Adding Schema Elements</a></li>
</ul>
-<h2 id="what-is-the-ldap-schema">What is the LDAP schema ?</h2>
+<h2 id="what-is-the-ldap-schema">What is the LDAP schema ?<a class="headerlink" href="#what-is-the-ldap-schema" title="Permanent link">¶</a></h2>
<p>It's a set of elements defining the data structure that can be stored in the server. It defines the following elements :</p>
<ul>
<li>AttributeType : the type of values that can be stored in an attribute</li>
@@ -187,7 +198,7 @@
<p>There are more schema elements which are not currently used in <em>Apache Directory Server</em>.</p>
<p>The following diagram shows all the interactions between each schema element :</p>
<p><img alt="Schema elements interactions" src="images/schema-objects.png" /></p>
-<h2 id="how-do-we-use-it-in-apacheds">How do we use it in ApacheDS ?</h2>
+<h2 id="how-do-we-use-it-in-apacheds">How do we use it in ApacheDS ?<a class="headerlink" href="#how-do-we-use-it-in-apacheds" title="Permanent link">¶</a></h2>
<p>The schema is everywhere in the server : each entry is controlled against the schema when it's added or modified. The schema is a critical part of the server.</p>
<p>The <em>Apache Directory Server</em> comes with a predefined schema, which should fit a large part of users need. You may though need to extend it...</p>
<p>Hopefully, the schema can be extended. This will be explained in the <em>Advanced User Guide</em>.</p>