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 [3/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/advanced-ug/4.2-authorization.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2-authorization.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2-authorization.html Sun Jul 5 22:34:35 2015
@@ -169,13 +169,24 @@
</div>
-<h1 id="42-authorization">4.2 - Authorization</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="42-authorization">4.2 - Authorization<a class="headerlink" href="#42-authorization" title="Permanent link">¶</a></h1>
<p>ApacheDS uses an adaptation of the X.500 basic access control scheme in
combination with X.500 subentries to control access to entries and
attributes within the DIT. This document will show you how to enable the
basic access control mechanism and how to define access control information
to manage access to protected resources.</p>
-<h2 id="chapter-content">Chapter content</h2>
+<h2 id="chapter-content">Chapter content<a class="headerlink" href="#chapter-content" title="Permanent link">¶</a></h2>
<ul>
<li><a href="4.2.1-introduction.html">4.2.1 - Introduction</a></li>
<li><a href="4.2.2-definitions.html">4.2.2 - Definitions</a></li>
@@ -189,7 +200,7 @@ to manage access to protected resources.
<li><a href="4.2.10-aci-grammar.html">4.2.10 - Aci Grammar</a></li>
<li><a href="4.2.11-links-and-references.html">4.2.11 - Links and References</a></li>
</ul>
-<h2 id="some-simple-examples">Some Simple Examples</h2>
+<h2 id="some-simple-examples">Some Simple Examples<a class="headerlink" href="#some-simple-examples" title="Permanent link">¶</a></h2>
<p>The ACIItem syntax is very expressive and that makes it extremely powerful
for specifying complex access control policies. However the syntax is not
very easy to grasp for beginners. For this reason we start with simple
@@ -208,7 +219,7 @@ following material.
Area for managing access control via prescriptiveACI. Both subentryACI and
prescriptiveACI require the presence of an Administrative Point entry. For
more information and code examples see <a href="acareas.html">ACAreas</a>. </p>
-<h3 id="aci-trails">ACI Trails</h3>
+<h3 id="aci-trails">ACI Trails<a class="headerlink" href="#aci-trails" title="Permanent link">¶</a></h3>
<p>Here are some trails that resemble simple HOWTO guides. They're ordered
with the most pragmatic usage first. We will add to these trails over
time.</p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.1-introduction.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.1-introduction.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.1-introduction.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="421-introduction">4.2.1 - Introduction</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="421-introduction">4.2.1 - Introduction<a class="headerlink" href="#421-introduction" title="Permanent link">¶</a></h1>
<p>First of all, one has to understand that Authorization in this context
involves four components. The principle is :</p>
<DIV class="info" markdown="1">
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.10-aci-grammar.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.10-aci-grammar.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.10-aci-grammar.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="4210-aci-grammar">4.2.10 - ACI grammar</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="4210-aci-grammar">4.2.10 - ACI grammar<a class="headerlink" href="#4210-aci-grammar" title="Permanent link">¶</a></h1>
<p>The ACI attributes store data following a specific structure, which is
define by this grammar :</p>
<div class="codehilite"><pre><wrapperEntryPoint> ::= <SP*> '{' <SP*> <mainACIItemComponent> <SP*>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.11-links-and-references.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.11-links-and-references.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.11-links-and-references.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="4211-links-and-references">4.2.11 Links and references</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="4211-links-and-references">4.2.11 Links and references<a class="headerlink" href="#4211-links-and-references" title="Permanent link">¶</a></h1>
<p>The <strong>Apache Directory Server</strong> authorization system is based on the <strong>X.500</strong>
specifications. Those documents are available on <a href="http://www.x500standard.com/index.php?n=Ig.LatestAvail">X.500 freely available specifications</a>
, and more specifically <a href="http://www.itu.int/rec/T-REC-X.501-200811-I!Cor2/dologin.asp?lang=e&id=T-REC-X.501-200811-I!Cor2!PDF-E&type=items">X.501</a>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.2-definitions.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.2-definitions.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.2-definitions.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="422-definitions">4.2.2 - Definitions</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="422-definitions">4.2.2 - Definitions<a class="headerlink" href="#422-definitions" title="Permanent link">¶</a></h1>
<p><strong>ACI</strong> :</p>
<blockquote>
<p>Access Control Information. The set of all the information which might
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.3-enabling-access-control.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.3-enabling-access-control.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.3-enabling-access-control.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="423-enabling-access-control">4.2.3 - Enabling Access Control</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="423-enabling-access-control">4.2.3 - Enabling Access Control<a class="headerlink" href="#423-enabling-access-control" title="Permanent link">¶</a></h1>
<p>TODO...</p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.4-aci-types.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.4-aci-types.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.4-aci-types.html Sun Jul 5 22:34:35 2015
@@ -169,11 +169,22 @@
</div>
-<h1 id="424-aci-types">4.2.4 - ACI types</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="424-aci-types">4.2.4 - ACI types<a class="headerlink" href="#424-aci-types" title="Permanent link">¶</a></h1>
<p>Three different types of ACI exist. All types use the same specification
syntax for an ACIITem. These types differ in their placement and manner of
use within the directory.</p>
-<h2 id="chapter-content">Chapter content</h2>
+<h2 id="chapter-content">Chapter content<a class="headerlink" href="#chapter-content" title="Permanent link">¶</a></h2>
<ul>
<li><a href="4.2.4.1-entryaci.html">4.2.4.1 - Entry Aci</a></li>
<li><a href="4.2.4.2-prescriptiveaci.html">4.2.4.2 - Prescriptive Aci</a></li>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.4.1-entryaci.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.4.1-entryaci.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.4.1-entryaci.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="4241-entryaci">4.2.4.1 - EntryACI</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="4241-entryaci">4.2.4.1 - EntryACI<a class="headerlink" href="#4241-entryaci" title="Permanent link">¶</a></h1>
<p>Entry ACI are access controls added to entries to protect that entry
specifically. Meaning the protected entry is the entry where the ACI
resides. When performing an operation on an entry, ApacheDS checks for the
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.4.2-prescriptiveaci.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.4.2-prescriptiveaci.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.4.2-prescriptiveaci.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="4242-prescriptiveaci">4.2.4.2 - PrescriptiveACI</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="4242-prescriptiveaci">4.2.4.2 - PrescriptiveACI<a class="headerlink" href="#4242-prescriptiveaci" title="Permanent link">¶</a></h1>
<p>Prescriptive ACI are access controls that are applied to a collection of
entries, not just to a single entry. Collections of entries are defined by
the subtreeSpecifications of subentries. Hence prescriptive ACI are added
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.4.3-subentryaci.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.4.3-subentryaci.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.4.3-subentryaci.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="4243-subentryaci">4.2.4.3 - SubentryACI</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="4243-subentryaci">4.2.4.3 - SubentryACI<a class="headerlink" href="#4243-subentryaci" title="Permanent link">¶</a></h1>
<p>Access to subentries also needs to be controlled. Subentries are special in
ApacheDS. Although they subordinate to an administrative entry (entry of an
Administrative Point), they are technically considered to be in the same
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5-aci-elements.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5-aci-elements.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5-aci-elements.html Sun Jul 5 22:34:35 2015
@@ -169,8 +169,19 @@
</div>
-<h1 id="425-aci-elements">4.2.5 - ACI elements</h1>
-<h2 id="chapter-content">Chapter content</h2>
+<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="425-aci-elements">4.2.5 - ACI elements<a class="headerlink" href="#425-aci-elements" title="Permanent link">¶</a></h1>
+<h2 id="chapter-content">Chapter content<a class="headerlink" href="#chapter-content" title="Permanent link">¶</a></h2>
<ul>
<li><a href="4.2.5.1-userclasses.html">4.2.5.1 - User Classes</a></li>
<li><a href="4.2.5.2-protecteditems.html">4.2.5.2 - User Protected Items</a></li>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5.1-userclasses.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5.1-userclasses.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5.1-userclasses.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="4251-userclasses">4.2.5.1 - UserClasses</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="4251-userclasses">4.2.5.1 - UserClasses<a class="headerlink" href="#4251-userclasses" title="Permanent link">¶</a></h1>
<p>TODO...</p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5.2-protecteditems.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5.2-protecteditems.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5.2-protecteditems.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="4252-protecteditems">4.2.5.2 - ProtectedItems</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="4252-protecteditems">4.2.5.2 - ProtectedItems<a class="headerlink" href="#4252-protecteditems" title="Permanent link">¶</a></h1>
<p>The <strong>protected items</strong> are elements being accessed, and thus controlled by
ACIs. Many parts of the DIT can be protected :</p>
<ul>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5.3-permissions.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5.3-permissions.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5.3-permissions.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="4553-permissions">4.5.5.3 - Permissions</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="4553-permissions">4.5.5.3 - Permissions<a class="headerlink" href="#4553-permissions" title="Permanent link">¶</a></h1>
<p>TODO...</p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5.4-subtrees.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5.4-subtrees.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5.4-subtrees.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="4554-subtrees">4.5.5.4 - Subtrees</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="4554-subtrees">4.5.5.4 - Subtrees<a class="headerlink" href="#4554-subtrees" title="Permanent link">¶</a></h1>
<p>TODO...</p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6-the-acdf-engine.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6-the-acdf-engine.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6-the-acdf-engine.html Sun Jul 5 22:34:35 2015
@@ -169,8 +169,19 @@
</div>
-<h1 id="426-the-acdf-engine">4.2.6 - The ACDF engine</h1>
-<h2 id="chapter-content">Chapter content</h2>
+<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="426-the-acdf-engine">4.2.6 - The ACDF engine<a class="headerlink" href="#426-the-acdf-engine" title="Permanent link">¶</a></h1>
+<h2 id="chapter-content">Chapter content<a class="headerlink" href="#chapter-content" title="Permanent link">¶</a></h2>
<ul>
<li><a href="4.2.6.1-how-it-works.html">4.2.6.1 - How it works</a></li>
<li><a href="4.2.6.2-selections.html">4.2.6.2 - Selections</a></li>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6.1-how-it-works.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6.1-how-it-works.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6.1-how-it-works.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="4261-how-it-works">4.2.6.1 - How it works</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="4261-how-it-works">4.2.6.1 - How it works<a class="headerlink" href="#4261-how-it-works" title="Permanent link">¶</a></h1>
<p>TODO...</p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6.2-selections.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6.2-selections.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6.2-selections.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="4262-selections">4.2.6.2 - Selections</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="4262-selections">4.2.6.2 - Selections<a class="headerlink" href="#4262-selections" title="Permanent link">¶</a></h1>
<p>TODO...</p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6.3-constraints.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6.3-constraints.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6.3-constraints.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="4263-constraints">4.2.6.3 - Constraints</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="4263-constraints">4.2.6.3 - Constraints<a class="headerlink" href="#4263-constraints" title="Permanent link">¶</a></h1>
<p>TODO...</p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6.4-priority.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6.4-priority.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6.4-priority.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="4264-priority">4.2.6.4 - Priority</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="4264-priority">4.2.6.4 - Priority<a class="headerlink" href="#4264-priority" title="Permanent link">¶</a></h1>
<p>TODO...</p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.7-using-acis-trail.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.7-using-acis-trail.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.7-using-acis-trail.html Sun Jul 5 22:34:35 2015
@@ -169,8 +169,19 @@
</div>
-<h1 id="427-using-acis-trail">4.2.7 - Using ACIs trail</h1>
-<h2 id="chapter-content">Chapter content</h2>
+<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="427-using-acis-trail">4.2.7 - Using ACIs trail<a class="headerlink" href="#427-using-acis-trail" title="Permanent link">¶</a></h1>
+<h2 id="chapter-content">Chapter content<a class="headerlink" href="#chapter-content" title="Permanent link">¶</a></h2>
<ul>
<li><a href="4.2.7.1-enable-authenticated-users-to-browse-and-read-entries.html">4.2.7.1 - Enable Authenticated Users to Browse and Read Entries</a></li>
<li><a href="4.2.7.2-allow-self-password-modify.html">4.2.7.2 - Allow Self Password Modify</a></li>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.7.1-enable-authenticated-users-to-browse-and-read-entries.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.7.1-enable-authenticated-users-to-browse-and-read-entries.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.7.1-enable-authenticated-users-to-browse-and-read-entries.html Sun Jul 5 22:34:35 2015
@@ -169,13 +169,24 @@
</div>
-<h1 id="4271-enable-authenticated-users-to-browse-and-read-entries">4.2.7.1 - Enable Authenticated Users to Browse and Read 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="4271-enable-authenticated-users-to-browse-and-read-entries">4.2.7.1 - Enable Authenticated Users to Browse and Read Entries<a class="headerlink" href="#4271-enable-authenticated-users-to-browse-and-read-entries" title="Permanent link">¶</a></h1>
<p>In this trail, we will show how we will allow all authenticated users to browse and read all the entries.</p>
<p>By default, if the access control subsystem is enabled, no one but the administrator can browse the DIT. This is obviously not convenient ...</p>
-<h1 id="partition-and-access-control-area-setup">Partition and Access Control Area Setup</h1>
+<h1 id="partition-and-access-control-area-setup">Partition and Access Control Area Setup<a class="headerlink" href="#partition-and-access-control-area-setup" title="Permanent link">¶</a></h1>
<p>For this example we presume you have setup a partition at the namingContext <strong>dc=example,dc=com</strong> and have turned on access controls. Now you want to grant browse and read access to entries and their attributes.</p>
<p>Before you can add a <strong>subentry</strong> with the <strong>prescriptiveACI</strong> you'll need to create an <strong>administrative area</strong>. For now we'll make the root of the partition the <strong>Administrative Point</strong> (<strong>AP</strong>). Every entry including this entry and those underneath will be part of the autonomous administrative area for managing access controls. To do this we must add the <strong>administrativeRole</strong> operational attribute to the <strong>AP</strong> entry. </p>
-<h2 id="administrationpoint-setup">AdministrationPoint setup</h2>
+<h2 id="administrationpoint-setup">AdministrationPoint setup<a class="headerlink" href="#administrationpoint-setup" title="Permanent link">¶</a></h2>
<p>In our case, the <strong>dc=example,dc=com</strong> context entry has to contain the <strong>administrativeRole</strong> attribute, with the <strong>accessControlSpecificArea</strong> value.</p>
<p>Let's first connect to the server using the <strong>admin</strong> user, and select the <strong>dc=example,dc=com</strong> entry :</p>
<p><img alt="dc=example.com" src="images/ACI-example.png" /></p>
@@ -185,10 +196,10 @@
<p><img alt="AccessControlSpecificArea" src="images/ACI-access-control-specific-area.png" /></p>
<p>Here is the resulting entry :</p>
<p><img alt="Result Entry" src="images/ACI-result-entry.png" /></p>
-<h2 id="subentry-addition">Subentry addition</h2>
+<h2 id="subentry-addition">Subentry addition<a class="headerlink" href="#subentry-addition" title="Permanent link">¶</a></h2>
<p>Now, we have to create a <strong>subentry</strong> in which we will add the <strong>prescriptiveACI</strong> granting access to all the users.</p>
<p>Let's define the ACI first.</p>
-<h3 id="aciitem-description">ACIItem Description</h3>
+<h3 id="aciitem-description">ACIItem Description<a class="headerlink" href="#aciitem-description" title="Permanent link">¶</a></h3>
<p>Here's the ACIItem we will add :</p>
<div class="codehilite"><pre><span class="o">{</span>
<span class="n">identificationTag</span> <span class="s">"enableSearchForAllUsers"</span><span class="o">,</span>
@@ -264,7 +275,7 @@ explanation of each field and it's meani
(<strong>grantBrowse</strong>), read the entries (<strong>grantRead</strong>) and return the DN for
aliases (<strong>grantReturnDN</strong>).</p>
<p><a name="2.5.7.1EnableAuthenticatedUserstoBrowseandReadEntries-PrescriptiveACIaddition"></a></p>
-<h2 id="prescriptiveaci-addition">PrescriptiveACI addition</h2>
+<h2 id="prescriptiveaci-addition">PrescriptiveACI addition<a class="headerlink" href="#prescriptiveaci-addition" title="Permanent link">¶</a></h2>
<p>Now that we have defined the <em>A</em>CIItem<strong>, we have to add it into a </strong>subentry<strong>
associated with the </strong>administration point<strong>. This is just an entry under the
</strong>administration Point<strong>, here, we will call it </strong>cn=enableSearchForAllUsers,
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.7.2-allow-self-password-modify.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.7.2-allow-self-password-modify.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.7.2-allow-self-password-modify.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="4272-allow-self-password-modify">4.2.7.2 - Allow Self Password Modify</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="4272-allow-self-password-modify">4.2.7.2 - Allow Self Password Modify<a class="headerlink" href="#4272-allow-self-password-modify" title="Permanent link">¶</a></h1>
<p>We will now configure the system to allow anyone to modify his/her own password :</p>
<div class="codehilite"><pre>{
identificationTag "allowSelfAccessAndModification",
@@ -188,7 +199,7 @@
</pre></div>
-<h2 id="commentary">Commentary</h2>
+<h2 id="commentary">Commentary<a class="headerlink" href="#commentary" title="Permanent link">¶</a></h2>
<p>Note that two different user permissions are used to accurately specify self access and self modification of the <strong>userPassword</strong> attribute within the entry. So with the first userPermission of this ACI a user would be able to read all attributes and values within his/her entry. They also have the ability to modify the entry but this is moot since they cannot add, remove or replace any attributes within their entry. The second user permission completes the picture by granting add and remove permissions to all values of userPassword. This means the user can replace the password.</p>
<DIV class="warning" markdown="1">
**grantAdd + grantRemove = grantReplace**
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.8-acis-administration.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.8-acis-administration.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.8-acis-administration.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="428-acis-administration">4.2.8 - ACIs administration</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="428-acis-administration">4.2.8 - ACIs administration<a class="headerlink" href="#428-acis-administration" title="Permanent link">¶</a></h1>
<p>TODO...</p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.9-migration-from-other-ldap-servers.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.9-migration-from-other-ldap-servers.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.9-migration-from-other-ldap-servers.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="459-migration-from-other-ldap-servers">4.5.9 - Migration from other LDAP servers</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="459-migration-from-other-ldap-servers">4.5.9 - Migration from other LDAP servers<a class="headerlink" href="#459-migration-from-other-ldap-servers" title="Permanent link">¶</a></h1>
<p>TODO...</p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.3-password-policy.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.3-password-policy.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.3-password-policy.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="43-password-policy">4.3. Password Policy</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="43-password-policy">4.3. Password Policy<a class="headerlink" href="#43-password-policy" title="Permanent link">¶</a></h1>
<p>The <strong>Password Policy for LDAP Directories</strong> is a <strong><a href="http://tools.ietf.org/html/draft-behera-ldap-password-policy-10">RFC</a></strong> draft that has been designed for the very first version in 1999, and the latest version is from 2009. Although it's still a draft, and it's currently noted as inactive, it has been implemented by many existing <strong>LDAP</strong> servers.</p>
<p><strong>ApacheDS</strong> implements most of the draft.</p>
<DIV class="warning" markdown="1">
@@ -180,7 +191,7 @@ Always try to think about better alterna
A long sentence (4 or 5 words), like "The horse has won the race three time" is most certainly a better password than any other combination, and is easy to remember...
</DIV>
-<h2 id="what-is-a-password-policy">What is a password policy ?</h2>
+<h2 id="what-is-a-password-policy">What is a password policy ?<a class="headerlink" href="#what-is-a-password-policy" title="Permanent link">¶</a></h2>
<p>As explained on <a href="http://en.wikipedia.org/wiki/Password_policy">wikipedia</a>:</p>
<div class="codehilite"><pre>A password policy is a set of rules designed to enhance computer security by encouraging users to employ strong passwords
and use them properly.
@@ -195,7 +206,7 @@ and use them properly.
<li>The password protection against attacks</li>
</ul>
<p>Those aspects are exposed in the following paragraphs.</p>
-<h2 id="how-do-we-configure-it">How do we configure it ?</h2>
+<h2 id="how-do-we-configure-it">How do we configure it ?<a class="headerlink" href="#how-do-we-configure-it" title="Permanent link">¶</a></h2>
<p>The <em>Password Policy</em> can be configured in two ways.
First of all, it's important to know that it's activated by default. Let's see the default configuration first.</p>
<p>There is an entry containing all the default configuration values for the <em>Password Policy</em>, under the DN <strong>"ou=passwordPolicies, ads-interceptorId=authenticationInterceptor, ou=interceptors, ads-directoryServiceId=<default>, ou=config"</strong>, which corresponds to the following hierarchy:</p>
@@ -369,11 +380,11 @@ All the configured delays are stored in
Note that the specification allows the administrator to apply the password policy on any attribute, with a default value of _userPassword_ ApacheDS does not yet allow the use of another Attribute.
</DIV>
-<h4 id="enablingdisabling-the-passwordpolicy">Enabling/Disabling the PasswordPolicy</h4>
+<h4 id="enablingdisabling-the-passwordpolicy">Enabling/Disabling the PasswordPolicy<a class="headerlink" href="#enablingdisabling-the-passwordpolicy" title="Permanent link">¶</a></h4>
<p>The <em>PasswordPolicy</em> is enabled by default. It's possible to disable it by setting the <em>ads-enabled</em> value to FALSE, with a server restart.</p>
-<h2 id="password-protection">Password protection</h2>
+<h2 id="password-protection">Password protection<a class="headerlink" href="#password-protection" title="Permanent link">¶</a></h2>
<p>This part is exposing the various techniques the system uses to protect your password from an attack.</p>
-<h3 id="password-guessing-limit">Password guessing limit</h3>
+<h3 id="password-guessing-limit">Password guessing limit<a class="headerlink" href="#password-guessing-limit" title="Permanent link">¶</a></h3>
<p>The idea is to protect the password against multiple guess attempts. The following rules are applied:</p>
<ul>
<li>a counter tracks the failed attempts, and blocks when it's reached</li>
@@ -381,7 +392,7 @@ Note that the specification allows the a
<li>a global delay for all the failed attempt is used, when reached, the account is locked</li>
</ul>
<p>When the account is locked, it can remain locked, or be unlocked after a grace period.</p>
-<h4 id="attempts-counter">Attempts counter</h4>
+<h4 id="attempts-counter">Attempts counter<a class="headerlink" href="#attempts-counter" title="Permanent link">¶</a></h4>
<DIV class="info" markdown="1">
Impacted Attributes: ads-pwdLockout, ads-pwdMaxFailure, ads-pwdLockoutDuration
</DIV>
@@ -455,22 +466,22 @@ In order to activate this control the ad
</tbody>
</table>
<p>As we can see, the account is locked only when we reach the number of failure, and the <em>ads-pwdLockout</em> flag is TRUE. If the <em>ads-pwdLockoutDuration</em> flag is set, then the password will remain locked for the delay stored in this attribute.</p>
-<h4 id="delayed-login">Delayed login</h4>
+<h4 id="delayed-login">Delayed login<a class="headerlink" href="#delayed-login" title="Permanent link">¶</a></h4>
<DIV class="info" markdown="1">
Impacted Attributes: ads-pwdLockout, ads-pwdMaxFailure, ads-pwdLockoutDuration
</DIV>
<p>When we have reached a number of failed attempt, the account will be locked. We can set another attribute to tell the server that the locked out account can be unlocked after a delay: the <em>ads-pwdLockoutDuration</em> Attribute stores this delay.</p>
<p>When the account is locked, no further attempt will succeed, even if the correct password is sent. After the delay, the user will be unlocked.</p>
-<h4 id="purging-failures">Purging failures</h4>
+<h4 id="purging-failures">Purging failures<a class="headerlink" href="#purging-failures" title="Permanent link">¶</a></h4>
<DIV class="info" markdown="1">
Impacted Attributes: ads-pwdFailureCountInterval
</DIV>
<p>As we store all the failures within the entry, at some point we may want to purge those failures. This is done either because we have successfully logged, or because the <em>ads-pwdFailureCountInterval</em> value has expired. In this last case, all the failures older than the current time minus the set interval will be removed.</p>
-<h3 id="password-checks-and-strength-enforcement">Password checks and strength enforcement</h3>
+<h3 id="password-checks-and-strength-enforcement">Password checks and strength enforcement<a class="headerlink" href="#password-checks-and-strength-enforcement" title="Permanent link">¶</a></h3>
<p>Those rules are used to enforce some constraints on the password, so that weak passwords can't be used.</p>
-<h4 id="quality-check-policy">Quality Check policy</h4>
+<h4 id="quality-check-policy">Quality Check policy<a class="headerlink" href="#quality-check-policy" title="Permanent link">¶</a></h4>
<DIV class="info" markdown="1">
Impacted Attributes: ads-pwdQualityCheck<br>
Default value: 1
@@ -483,21 +494,21 @@ We use a parameter to specify the kind o
<li>1: We check the password when we can, i.e. when it's not hashed. When the password is hashed, or in a form that does not allow us to apply the checks, then we ignore the errors</li>
<li>2: The password is checked, and if it's hashed or in a form that does not allow the checks to be done, then the changes are rejected.</li>
</ul>
-<h4 id="password-history">Password History</h4>
+<h4 id="password-history">Password History<a class="headerlink" href="#password-history" title="Permanent link">¶</a></h4>
<DIV class="info" markdown="1">
Impacted Attributes: ads-pwdInHistory
</DIV>
<p>The server can keep a backlog of passwords, so that a user can't keep a password for ever. When requested to do so the user will have to change his/her password, and the old password will be stored in the user's entry password history.</p>
<p>We can specify the number of passwords we keep in the password history by configuring the <em>ads-pwdInHistory</em> attribute.</p>
-<h4 id="minimum-delay-between-modifications">Minimum delay between modifications</h4>
+<h4 id="minimum-delay-between-modifications">Minimum delay between modifications<a class="headerlink" href="#minimum-delay-between-modifications" title="Permanent link">¶</a></h4>
<DIV class="info" markdown="1">
Impacted Attributes: ads-pwdMinAge
</DIV>
<p>When the password history is activated, some users may change their passwords many times to get their old password out of the history, and add it as their password again. Setting a delay between two password changes may protect the password against such action.</p>
<p>The <em>ads-pwdMinAge</em> attribute is used for this purpose, and it keeps a value in seconds.</p>
-<h4 id="password-length-constraint">Password length constraint</h4>
+<h4 id="password-length-constraint">Password length constraint<a class="headerlink" href="#password-length-constraint" title="Permanent link">¶</a></h4>
<DIV class="info" markdown="1">
Impacted Attributes: ads-pwdMinLength and ads-pwdMaxLength
</DIV>
@@ -507,9 +518,9 @@ Impacted Attributes: ads-pwdMinLength an
Setting a password max length is most certainly a waste of time. It's very likely that this parameter has been added to the specification for the sake of symetry...
</DIV>
-<h3 id="password-lifecycle-management">Password lifecycle management</h3>
+<h3 id="password-lifecycle-management">Password lifecycle management<a class="headerlink" href="#password-lifecycle-management" title="Permanent link">¶</a></h3>
<p>We now have to expose the rules that apply to the password during it's life.</p>
-<h4 id="password-max-age">Password max age</h4>
+<h4 id="password-max-age">Password max age<a class="headerlink" href="#password-max-age" title="Permanent link">¶</a></h4>
<DIV class="info" markdown="1">
Impacted Attribute: ads-pwdMaxAge
</DIV>
@@ -520,38 +531,38 @@ Impacted Attribute: ads-pwdMaxAge
This parameter works hands in hands with some other parameter, like the ads-pwdGraceAuthNLimit and ads-GraceExpire. If those parameters are set too, you may get some different delay for your password expiration.
</DIV>
-<h4 id="password-grace-auth-n-limit">Password grace auth N limit</h4>
+<h4 id="password-grace-auth-n-limit">Password grace auth N limit<a class="headerlink" href="#password-grace-auth-n-limit" title="Permanent link">¶</a></h4>
<DIV class="info" markdown="1">
Impacted Attribute: ads-pwdGraceAuthNLimit
</DIV>
<p>When the password has expired, this parameter (<em>ads-pwdGraceAuthNLimit</em>) tells how many times a user will still be allowed to bind before the password is definitively locked. Each attempt will decrement the associated counter.</p>
-<h4 id="password-grace-expire">Password grace Expire</h4>
+<h4 id="password-grace-expire">Password grace Expire<a class="headerlink" href="#password-grace-expire" title="Permanent link">¶</a></h4>
<DIV class="info" markdown="1">
Impacted Attribute: ads-pwdGraceExpire
</DIV>
<p>Another option when the password has expired is to give the user the possibility to log in during a certain period of time. This is mainly useful when the <em>ads-pwdGraceAuthNLimit</em> is set: not only there is a limited number of attempts, but those attempts must be done in a limited period of time, ortherwise the password will be locked.</p>
<p>If the configuration of the <em>ads-pwdGraceAuthNLimit</em> is 0, the <em>ads-pwdGraceExpire</em> value is simply added to the <em>ads-pwdMaxAge</em> value.</p>
-<h4 id="idle-password">Idle Password</h4>
+<h4 id="idle-password">Idle Password<a class="headerlink" href="#idle-password" title="Permanent link">¶</a></h4>
<DIV class="info" markdown="1">
Impacted Attribute: ads-pwdMaxIdle
</DIV>
<p>You can set a maximum inactivity delay for a password, before this password expires. This is set using the <em>ads-pwdMaxIdle</em> parameter</p>
-<h4 id="expiration-warning">Expiration warning</h4>
+<h4 id="expiration-warning">Expiration warning<a class="headerlink" href="#expiration-warning" title="Permanent link">¶</a></h4>
<DIV class="info" markdown="1">
Impacted Attribute: ads-pwdExpireWarning
</DIV>
<p>The <em>ads-pwdExpireWarning</em> parameter will be used to send back a warning if the password if the password is going to expire in a given delay. This is convenient as soon as the client sends the <em>PasswordPolicy</em> control to the server, and as soon as the client reads the response's control.</p>
-<h4 id="allow-user-changes">Allow user changes</h4>
+<h4 id="allow-user-changes">Allow user changes<a class="headerlink" href="#allow-user-changes" title="Permanent link">¶</a></h4>
<DIV class="info" markdown="1">
Impacted Attribute: ads-pwdAllowUserChange
</DIV>
<p>The <em>ads-pwdAllowUserChange</em> parameter can be used to allow - or forbid - a user to change his/her own password. When this parameter is set to <em>TRUE</em>, the user can't change his/her password.</p>
-<h3 id="not-supported-parameters">Not supported parameters</h3>
+<h3 id="not-supported-parameters">Not supported parameters<a class="headerlink" href="#not-supported-parameters" title="Permanent link">¶</a></h3>
<p>A few parameters are described in the specification, but aren't supported. Here is the list :</p>
<ul>
<li>ads-pwdMinDelay : The minimal delay the server waits before sending back a response.</li>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/5-administration.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/5-administration.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/5-administration.html Sun Jul 5 22:34:35 2015
@@ -169,9 +169,20 @@
</div>
-<h1 id="5-administration">5 - Administration</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="5-administration">5 - Administration<a class="headerlink" href="#5-administration" title="Permanent link">¶</a></h1>
<p>This chapter describe how to administer the <strong>Apache Directory Server</strong>.</p>
-<h2 id="chapter-content">Chapter content</h2>
+<h2 id="chapter-content">Chapter content<a class="headerlink" href="#chapter-content" title="Permanent link">¶</a></h2>
<ul>
<li><a href="5.1-layout.html">5.1 - Layout</a></li>
<li><a href="5.2-start-stop.html">5.2 - Starting and stopping the server</a></li>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/5.1-layout.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/5.1-layout.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/5.1-layout.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="51-layout">5.1 - Layout</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="51-layout">5.1 - Layout<a class="headerlink" href="#51-layout" title="Permanent link">¶</a></h1>
<div class="toc">
<ul>
<li><a href="#51-layout">5.1 - Layout</a><ul>
@@ -189,13 +200,13 @@
</li>
</ul>
</div>
-<h2 id="511-general-layout">5.1.1 General Layout</h2>
+<h2 id="511-general-layout">5.1.1 General Layout<a class="headerlink" href="#511-general-layout" title="Permanent link">¶</a></h2>
<p>The general layout for ApacheDS is fairly simple and consists in two major concepts:</p>
<ul>
<li>an installation layout</li>
<li>an instance layout</li>
</ul>
-<h3 id="5111-installation-layout">5.1.1.1 Installation Layout</h3>
+<h3 id="5111-installation-layout">5.1.1.1 Installation Layout<a class="headerlink" href="#5111-installation-layout" title="Permanent link">¶</a></h3>
<p>The installation is where are stored all files essential to ApacheDS like the launch script, libraries, eventually a service wrapper (depending on the kind of installer used).</p>
<p>The most common installation, shared by all ApacheDS installers, can be described as follows:</p>
<div class="codehilite"><pre>[Installation-Layout]
@@ -220,7 +231,7 @@
<li>The <em><strong>lib/</strong></em> directory contains all ApacheDS and wrapper libraries necessary to run the server.</li>
<li><em><strong>LICENCE</strong></em> and <em><strong>NOTICE</strong></em> files contains the required legal information about ApacheDS.</li>
</ul>
-<h3 id="5112-instance-layout">5.1.1.2 Instance Layout</h3>
+<h3 id="5112-instance-layout">5.1.1.2 Instance Layout<a class="headerlink" href="#5112-instance-layout" title="Permanent link">¶</a></h3>
<p>ApacheDS is built to be able to run multiple instances of the server at the same time, which means that optionally an <em><strong>instances</strong></em> folder can be found in the installation layout (or elsewhere on disk depending on the platform).
In that folder, can be found a single or multiple directories, all sharing the same layout, corresponding to all ApacheDS instance (one directory per instance, named by the id of the instance).</p>
<p>Here's how this instance layout can be described:</p>
@@ -263,9 +274,9 @@ In that folder, can be found a single or
</ul>
</li>
</ul>
-<h2 id="512-specific-layouts">5.1.2 Specific Layouts</h2>
+<h2 id="512-specific-layouts">5.1.2 Specific Layouts<a class="headerlink" href="#512-specific-layouts" title="Permanent link">¶</a></h2>
<p>Depending on the type of distribution used to install ApacheDS, the layout varies to adapt as best as possible to the specificities of each platform.</p>
-<h3 id="5121-archive-distribution-ziptargz">5.1.2.1 Archive Distribution (zip/tar.gz)</h3>
+<h3 id="5121-archive-distribution-ziptargz">5.1.2.1 Archive Distribution (zip/tar.gz)<a class="headerlink" href="#5121-archive-distribution-ziptargz" title="Permanent link">¶</a></h3>
<p>The Archive distribution consist of a compressed directory containing everything needed to run ApacheDS. It doesn't install on the machine and does not require any extra permission (root user, installer password, etc.). The directory is simply unarchived and ApacheDS is ready to be launched.</p>
<p>The installation layout is a bit simpler for this kind of distribution since no wrapper is distributed, the application being run in a terminal or via the .bat script.</p>
<div class="codehilite"><pre>[Installation-Layout]
@@ -287,7 +298,7 @@ In that folder, can be found a single or
<li>The <em><strong>lib/</strong></em> directory only contains the ApacheDS library.</li>
<li><em><strong>LICENCE</strong></em> and <em><strong>NOTICE</strong></em> files contains the required legal information about ApacheDS.</li>
</ul>
-<h3 id="5122-windows-installer-exe">5.1.2.2 Windows Installer (.exe)</h3>
+<h3 id="5122-windows-installer-exe">5.1.2.2 Windows Installer (.exe)<a class="headerlink" href="#5122-windows-installer-exe" title="Permanent link">¶</a></h3>
<p>The Windows installer uses the general installation and instances layout.</p>
<p>By default, the installation directory is:</p>
<div class="codehilite"><pre><span class="n">C</span><span class="p">:</span><span class="o">\</span><span class="n">Program</span> <span class="n">Files</span><span class="o">\</span><span class="n">ApacheDS</span>
@@ -296,7 +307,7 @@ In that folder, can be found a single or
<p>An <em><strong>instances/</strong></em> directory in the installation layout holds all ApacheDS instances (an instance named <em><strong>default</strong></em> is provided by default).</p>
<p>ApacheDS is registered as a service on Windows. Operations on the service can be achieved in the <em><strong>Services</strong></em> utility which is accessible via <em><strong>Start</strong></em> > <em><strong>Contol Panel</strong></em> > <em><strong>Administration Tools</strong></em> > <em><strong>Services</strong></em>.</p>
-<h3 id="5123-linux-binary-bin-debian-deb-fedora-rpm-installers">5.1.2.3 Linux Binary (.bin), Debian (.deb) & Fedora (.rpm) Installers</h3>
+<h3 id="5123-linux-binary-bin-debian-deb-fedora-rpm-installers">5.1.2.3 Linux Binary (.bin), Debian (.deb) & Fedora (.rpm) Installers<a class="headerlink" href="#5123-linux-binary-bin-debian-deb-fedora-rpm-installers" title="Permanent link">¶</a></h3>
<p>The Mac OS X installer uses the general installation and instances layout.</p>
<p>By default, the installation directory is:</p>
<div class="codehilite"><pre>/opt/apacheds-<span class="cp">${</span><span class="n">version</span><span class="cp">}</span>
@@ -314,7 +325,7 @@ In that folder, can be found a single or
<p><strong>NOTE:</strong> The ApacheDS Linux Binary installer lets the user decide the locations of the installation directory, the instances directory and the default instance launch script. The locations above refer to the default location and need to be adapted to whatever path was chosen during the installation.</p>
-<h3 id="5124-mac-os-x-installer-pkg">5.1.2.4 Mac OS X Installer (.pkg)</h3>
+<h3 id="5124-mac-os-x-installer-pkg">5.1.2.4 Mac OS X Installer (.pkg)<a class="headerlink" href="#5124-mac-os-x-installer-pkg" title="Permanent link">¶</a></h3>
<p>The Mac OS X installer uses the general installation and instances layout.</p>
<p>By default, the installation directory is:</p>
<div class="codehilite"><pre>/usr/local/apacheds-<span class="cp">${</span><span class="n">version</span><span class="cp">}</span>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/5.2-start-stop.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/5.2-start-stop.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/5.2-start-stop.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="52-starting-and-stopping-the-server">5.2 - Starting and Stopping 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="52-starting-and-stopping-the-server">5.2 - Starting and Stopping the server<a class="headerlink" href="#52-starting-and-stopping-the-server" title="Permanent link">¶</a></h1>
<div class="toc">
<ul>
<li><a href="#52-starting-and-stopping-the-server">5.2 - Starting and Stopping the server</a><ul>
@@ -201,53 +212,53 @@
</li>
</ul>
</div>
-<h2 id="521-archive-distribution-ziptargz">5.2.1 Archive Distribution (zip/tar.gz)</h2>
-<h3 id="starting-apacheds">Starting ApacheDS</h3>
-<h4 id="on-linuxunix-systems">On Linux/Unix Systems</h4>
+<h2 id="521-archive-distribution-ziptargz">5.2.1 Archive Distribution (zip/tar.gz)<a class="headerlink" href="#521-archive-distribution-ziptargz" title="Permanent link">¶</a></h2>
+<h3 id="starting-apacheds">Starting ApacheDS<a class="headerlink" href="#starting-apacheds" title="Permanent link">¶</a></h3>
+<h4 id="on-linuxunix-systems">On Linux/Unix Systems<a class="headerlink" href="#on-linuxunix-systems" title="Permanent link">¶</a></h4>
<p>In a terminal, first move to the ApacheDS directory of the unarchived distribution and then run the <em><strong>apacheds.sh</strong></em> script in the <em><strong>bin</strong></em> directory:</p>
<div class="codehilite"><pre>$ <span class="n">cd</span> <span class="o"><</span><span class="n">path</span><span class="o">-</span><span class="n">to</span><span class="o">-</span><span class="n">apacheds</span><span class="o">-</span><span class="n">directory</span><span class="o">></span>
$ <span class="n">sh</span> <span class="n">bin</span><span class="o">/</span><span class="n">apache</span><span class="p">.</span><span class="n">sh</span>
</pre></div>
-<h4 id="on-windows">On Windows</h4>
+<h4 id="on-windows">On Windows<a class="headerlink" href="#on-windows" title="Permanent link">¶</a></h4>
<p>Double-click the <em><strong>apacheds.bat</strong></em> command in the <em><strong>bin</strong></em> directory or in a terminal, first move to the <em><strong>bin</strong></em> directory of the unarchived distribution and then run the <em><strong>apacheds.bat</strong></em> command:</p>
<div class="codehilite"><pre>$ <span class="n">cd</span> <span class="o"><</span><span class="n">path</span><span class="o">-</span><span class="n">to</span><span class="o">-</span><span class="n">apacheds</span><span class="o">-</span><span class="n">directory</span><span class="o">>\</span><span class="n">bin</span>
$ <span class="n">apacheds</span><span class="p">.</span><span class="n">bat</span>
</pre></div>
-<h3 id="stopping-apacheds">Stopping ApacheDS</h3>
+<h3 id="stopping-apacheds">Stopping ApacheDS<a class="headerlink" href="#stopping-apacheds" title="Permanent link">¶</a></h3>
<p>ApacheDS can be stopped by hitting <em><strong>CTL+C</strong></em> in the terminal the server was launched with. If the <em><strong>apacheds.bat</strong></em> command was double-clicked, closing the terminal window will also stop ApacheDS. </p>
-<h2 id="522-windows-installer-exe">5.2.2 Windows Installer (.exe)</h2>
+<h2 id="522-windows-installer-exe">5.2.2 Windows Installer (.exe)<a class="headerlink" href="#522-windows-installer-exe" title="Permanent link">¶</a></h2>
<p>ApacheDS is registered as a service on Windows. Start and Stop operations can be achieved in the <em><strong>Services</strong></em> utility which is accessible via <em><strong>Start</strong></em> > <em><strong>Control Panel</strong></em> > <em><strong>Administration Tools</strong></em> > <em><strong>Services</strong></em>.</p>
<p>ApacheDS also provides an easier access to the <em><strong>Services</strong></em> utility via <em><strong>Start</strong></em> > <em><strong>All Programs</strong></em> > <em><strong>ApacheDS</strong></em> > <em><strong>Manage ApacheDS</strong></em>. </p>
-<h3 id="starting-apacheds_1">Starting ApacheDS</h3>
+<h3 id="starting-apacheds_1">Starting ApacheDS<a class="headerlink" href="#starting-apacheds_1" title="Permanent link">¶</a></h3>
<p>The ApacheDS service can be started right-clicking on the <em><strong>ApacheDS - Default</strong></em> service and selecting <em><strong>Start</strong></em> in the context menu.</p>
-<h3 id="stopping-apacheds_1">Stopping ApacheDS</h3>
+<h3 id="stopping-apacheds_1">Stopping ApacheDS<a class="headerlink" href="#stopping-apacheds_1" title="Permanent link">¶</a></h3>
<p>The ApacheDS service can be started right-clicking on the <em><strong>ApacheDS - Default</strong></em> service and selecting <em><strong>Stop</strong></em> in the context menu.</p>
-<h2 id="523-linux-binary-bin-debian-deb-fedora-rpm-installers">5.2.3 Linux Binary (.bin), Debian (.deb) & Fedora (.rpm) Installers</h2>
-<h3 id="starting-apacheds_2">Starting ApacheDS</h3>
+<h2 id="523-linux-binary-bin-debian-deb-fedora-rpm-installers">5.2.3 Linux Binary (.bin), Debian (.deb) & Fedora (.rpm) Installers<a class="headerlink" href="#523-linux-binary-bin-debian-deb-fedora-rpm-installers" title="Permanent link">¶</a></h2>
+<h3 id="starting-apacheds_2">Starting ApacheDS<a class="headerlink" href="#starting-apacheds_2" title="Permanent link">¶</a></h3>
<p>In a terminal, run the following command:</p>
<div class="codehilite"><pre>$ sudo /etc/init.d/apacheds-<span class="cp">${</span><span class="n">version</span><span class="cp">}</span>-default start
</pre></div>
-<h3 id="stopping-apacheds_2">Stopping ApacheDS</h3>
+<h3 id="stopping-apacheds_2">Stopping ApacheDS<a class="headerlink" href="#stopping-apacheds_2" title="Permanent link">¶</a></h3>
<p>In a terminal, run the following command:</p>
<div class="codehilite"><pre>$ sudo /etc/init.d/apacheds-<span class="cp">${</span><span class="n">version</span><span class="cp">}</span>-default stop
</pre></div>
<p><strong>NOTE:</strong> The ApacheDS Linux Binary installer lets the user decide the location of the launch script. The commands above refer to the default location and need to be adapted to whatever path was chosen during the installation.</p>
-<h2 id="524-mac-os-x-installer-pkg">5.2.4 Mac OS X Installer (.pkg)</h2>
-<h3 id="starting-apacheds_3">Starting ApacheDS</h3>
+<h2 id="524-mac-os-x-installer-pkg">5.2.4 Mac OS X Installer (.pkg)<a class="headerlink" href="#524-mac-os-x-installer-pkg" title="Permanent link">¶</a></h2>
+<h3 id="starting-apacheds_3">Starting ApacheDS<a class="headerlink" href="#starting-apacheds_3" title="Permanent link">¶</a></h3>
<p>In a terminal, run the following command:</p>
<div class="codehilite"><pre>$ <span class="n">sudo</span> <span class="n">launchctl</span> <span class="n">start</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>
</pre></div>
-<h3 id="stopping-apacheds_3">Stopping ApacheDS</h3>
+<h3 id="stopping-apacheds_3">Stopping ApacheDS<a class="headerlink" href="#stopping-apacheds_3" title="Permanent link">¶</a></h3>
<p>In a terminal, run the following command:</p>
<div class="codehilite"><pre>$ <span class="n">sudo</span> <span class="n">launchctl</span> <span class="n">stop</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>
</pre></div>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/5.3-logs.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/5.3-logs.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/5.3-logs.html Sun Jul 5 22:34:35 2015
@@ -169,8 +169,19 @@
</div>
-<h1 id="53-logs">5.3 - Logs</h1>
-<h2 id="531-logs-overview">5.3.1 Logs overview</h2>
+<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="53-logs">5.3 - Logs<a class="headerlink" href="#53-logs" title="Permanent link">¶</a></h1>
+<h2 id="531-logs-overview">5.3.1 Logs overview<a class="headerlink" href="#531-logs-overview" title="Permanent link">¶</a></h2>
<p>ApacheDS internally uses SLF4J as a facade for logs and Log4J is bundled in the standalone ApacheDS distributions. </p>
<p>Logs can be configured by modifying the <em><strong>log4j.properties</strong></em> file which can be found in the <em><strong>conf</strong></em> directory of the server instance (see the previous chapter "<a href="5.1-layout.html">5.1 - Layout</a>").</p>
<p>Here is the Log4J configuration that comes with ApacheDS:</p>
@@ -215,7 +226,7 @@ log4j.appender.F.layout.ConversionPatter
</pre></div>
-<h2 id="532-default-log-level">5.3.2 Default log level</h2>
+<h2 id="532-default-log-level">5.3.2 Default log level<a class="headerlink" href="#532-default-log-level" title="Permanent link">¶</a></h2>
<p>By default, ApacheDS ships with a default log level set to <strong>WARN</strong> as indicated in the first line of the <em><strong>log4j.properties</strong></em> file:</p>
<div class="codehilite"><pre>log4j.rootCategory=WARN, F
</pre></div>
@@ -263,7 +274,7 @@ log4j.appender.F.layout.ConversionPatter
</table>
<p></center></p>
<p>Please refer to the <a href="http://logging.apache.org/log4j/1.2/manual.html"><strong>Log4J Manual</strong></a> for more details.</p>
-<h2 id="532-apacheds-specific-loggers">5.3.2 ApacheDS specific loggers</h2>
+<h2 id="532-apacheds-specific-loggers">5.3.2 ApacheDS specific loggers<a class="headerlink" href="#532-apacheds-specific-loggers" title="Permanent link">¶</a></h2>
<p>Bundled at the end of the <em><strong>log4j.properties</strong></em> file, are a set of specific loggers dedicated to a particular kind of events:</p>
<div class="codehilite"><pre># Specific loggers (useful for debugging)
#log4j.logger.jdbm.recman.BaseRecordManager=DEBUG
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/5.4-replication.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/5.4-replication.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/5.4-replication.html Sun Jul 5 22:34:35 2015
@@ -169,10 +169,21 @@
</div>
-<h1 id="54-replication">5.4 - Replication</h1>
-<h2 id="541-replication-overview">5.4.1 Replication overview</h2>
+<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="54-replication">5.4 - Replication<a class="headerlink" href="#54-replication" title="Permanent link">¶</a></h1>
+<h2 id="541-replication-overview">5.4.1 Replication overview<a class="headerlink" href="#541-replication-overview" title="Permanent link">¶</a></h2>
<p>ApacheDS supports both Master-Slave and Multi-Master replication based on the <a href="http://tools.ietf.org/html/rfc4533">syncrepl</a> specification.</p>
-<h2 id="initial-steps">Initial steps</h2>
+<h2 id="initial-steps">Initial steps<a class="headerlink" href="#initial-steps" title="Permanent link">¶</a></h2>
<p>The below initial conditions must be met before configuring the replication in any mode.</p>
<ul>
<li>
@@ -185,7 +196,7 @@
See <a href="../basic-ug/1.4.3-adding-partition.mdtext">Adding Partition</a></p>
</li>
</ul>
-<h2 id="configuring-master-slave-replication">Configuring Master-Slave replication</h2>
+<h2 id="configuring-master-slave-replication">Configuring Master-Slave replication<a class="headerlink" href="#configuring-master-slave-replication" title="Permanent link">¶</a></h2>
<p>Assuming that the master is running on localhost at port 10389 and slave on localhost at port 11997 and we want to
replicate the data from partition dc=apache,dc=org</p>
<p>The below configuration must be added in the slave server and restart slave.</p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/6-implementing-interceptor.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/6-implementing-interceptor.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/6-implementing-interceptor.html Sun Jul 5 22:34:35 2015
@@ -169,10 +169,21 @@
</div>
-<h1 id="6-implementing-a-simple-custom-interceptor-for-apacheds">6 - Implementing a simple custom Interceptor for ApacheDS</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="6-implementing-a-simple-custom-interceptor-for-apacheds">6 - Implementing a simple custom Interceptor for ApacheDS<a class="headerlink" href="#6-implementing-a-simple-custom-interceptor-for-apacheds" title="Permanent link">¶</a></h1>
<p>This site was updated for ApacheDS 2.0.</p>
<p>The following is for developers who plan to implement their own interceptors in order to extend or modify the functionality of Apache Directory Server. It contains a simple example as a starting point.</p>
-<h2 id="what-exactly-is-an-interceptor">What exactly is an interceptor?</h2>
+<h2 id="what-exactly-is-an-interceptor">What exactly is an interceptor?<a class="headerlink" href="#what-exactly-is-an-interceptor" title="Permanent link">¶</a></h2>
<p>An interceptor filters method calls performed on on the DefaultPartitionNexus just like Servlet filters do. The ApacheDS configuration contains a chain of filters performing several tasks. In order to illustrate this, here is the list of interceptors from the default server configuration of ApacheDS 2.0</p>
<div class="codehilite"><pre><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">core</span><span class="p">.</span><span class="n">normalization</span><span class="p">.</span><span class="n">NormalizationInterceptor</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">core</span><span class="p">.</span><span class="n">authn</span><span class="p">.</span><span class="n">AuthenticationInterceptor</span>
@@ -206,7 +217,7 @@ Password hash. A simple interceptor</p>
</pre></div>
-<h2 id="the-sources">The sources</h2>
+<h2 id="the-sources">The sources<a class="headerlink" href="#the-sources" title="Permanent link">¶</a></h2>
<p>Currently, the sources are checked in here</p>
<div class="codehilite"><pre><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">svn</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">directory</span><span class="o">/</span><span class="n">sandbox</span><span class="o">/</span><span class="n">szoerner</span><span class="o">/</span><span class="n">passwordHashInterceptor</span>
</pre></div>
@@ -305,7 +316,7 @@ Implementing the class PasswordHashInter
</pre></div>
-<h2 id="using-the-interceptor">Using the interceptor</h2>
+<h2 id="using-the-interceptor">Using the interceptor<a class="headerlink" href="#using-the-interceptor" title="Permanent link">¶</a></h2>
<p>You may use a custom interceptor both in a standard ApacheDS installation and in a server started embedded.
Adding it to a standard server installation (server.xml)</p>
<p>In order to get the interceptor installed in a default installation of ApacheDS 1.5.5., just copy the jar-File resulting from the Maven build, which contains the custom classes, to APACHEDS_INSTALLDIR/lib/ext.</p>
@@ -329,7 +340,7 @@ Adding it to a standard server installat
</pre></div>
-<h2 id="embedded-mode">Embedded mode</h2>
+<h2 id="embedded-mode">Embedded mode<a class="headerlink" href="#embedded-mode" title="Permanent link">¶</a></h2>
<p>As an alternative, the following Java code starts an ApacheDS embedded in a main method. The list of interceptors is complemented with the example interceptor. We insert it exactly behind the NormalizingInterceptor (the position is a little bit tricky to determine).</p>
<div class="codehilite"><pre><span class="n">package</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">samples</span><span class="p">.</span><span class="n">interceptor</span><span class="p">.</span><span class="n">pwdhash</span><span class="p">;</span>
@@ -382,7 +393,7 @@ Adding it to a standard server installat
</pre></div>
-<h2 id="verification">Verification</h2>
+<h2 id="verification">Verification<a class="headerlink" href="#verification" title="Permanent link">¶</a></h2>
<p>Let's check whether our new interceptor does its job! In order to do so, we use Apache Directory Studio and connect to the server with the interceptor enabled (see above).</p>
<p>First we create a new entry with the following data, using "New Entry ..." within Studio.</p>
<div class="codehilite"><pre><span class="n">dn</span><span class="o">:</span> <span class="n">cn</span><span class="o">=</span><span class="n">Kate</span> <span class="n">Bush</span><span class="o">,</span><span class="n">ou</span><span class="o">=</span><span class="n">users</span><span class="o">,</span><span class="n">ou</span><span class="o">=</span><span class="n">system</span>
@@ -414,7 +425,7 @@ $
</pre></div>
-<h2 id="limitations-of-the-example">Limitations of the example</h2>
+<h2 id="limitations-of-the-example">Limitations of the example<a class="headerlink" href="#limitations-of-the-example" title="Permanent link">¶</a></h2>
<p>This example is intended as a demonstration, on how to write your custom interceptor. Don't consider it bullet proof. It has not been tested under production conditions, etc.</p>
<p>At least the following limitation should be mentioned</p>
<div class="codehilite"><pre><span class="n">The</span> <span class="n">default</span> <span class="n">hash</span> <span class="n">algorithm</span> <span class="n">MD5</span> <span class="n">is</span> <span class="n">considered</span> <span class="n">weak</span><span class="p">.</span>
@@ -423,7 +434,7 @@ $
</pre></div>
-<h2 id="further-reading">Further reading</h2>
+<h2 id="further-reading">Further reading<a class="headerlink" href="#further-reading" title="Permanent link">¶</a></h2>
<p>Learn more about interceptors in ApacheDS Architecture Documentation, check out the source code of some implementations of the Interceptor interface, and/or read the javadoc comments.</p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/7-embedding-apacheds.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/7-embedding-apacheds.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/7-embedding-apacheds.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="7-embedding-apacheds-in-java">7 - Embedding ApacheDS in Java</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="7-embedding-apacheds-in-java">7 - Embedding ApacheDS in Java<a class="headerlink" href="#7-embedding-apacheds-in-java" title="Permanent link">¶</a></h1>
<p>TODO...</p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-user-guide.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-user-guide.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-user-guide.html Sun Jul 5 22:34:35 2015
@@ -150,9 +150,20 @@
-<h1 id="apacheds-20-advanced-user-guide">ApacheDS 2.0 Advanced User Guide</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="apacheds-20-advanced-user-guide">ApacheDS 2.0 Advanced User Guide<a class="headerlink" href="#apacheds-20-advanced-user-guide" title="Permanent link">¶</a></h1>
<p>This guide get you a deep further into ApacheDS 2.0. Once you have installed the server, and undestood how it works, this is the guide to read to get a complete understanding on what it offers, and how to use it at full steam.</p>
-<h1 id="table-of-content">Table of content</h1>
+<h1 id="table-of-content">Table of content<a class="headerlink" href="#table-of-content" title="Permanent link">¶</a></h1>
<ul>
<li><a href="advanced-ug/0-community.html">0 - Community</a><ul>
<li><a href="advanced-ug/0.1-reporting-bugs.html">0.1. Reporting Bugs</a></li>
Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/1-how-to-begin.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/1-how-to-begin.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/1-how-to-begin.html Sun Jul 5 22:34:35 2015
@@ -169,10 +169,21 @@
</div>
-<h1 id="1-how-to-begin">1 - How to begin</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="1-how-to-begin">1 - How to begin<a class="headerlink" href="#1-how-to-begin" title="Permanent link">¶</a></h1>
<p>This chapter helps you to set up a server, with the minimal configuration options being explained. That should be enough to get a running server.</p>
<p>This user guide is <strong>not</strong> intended to be a <strong>LDAP</strong> guide : there are some excellent tutorials or books, we won't try to challenge them !</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.1-what-apacheds-is.html">1.1 - What Apache Directory Server is</a></li>
<li><a href="1.2-some-background.html">1.2 - Some Background. Directories, directory services and LDAP</a></li>