svn commit: r1016727 - in /websites/staging/directory/trunk/content: ./ apacheds/advanced-ug/4.2.7.1-enable-authenticated-users-to-browse-and-read-entries.html

[bu...@apache.org]

Author: buildbot
Date: Sun Aug 13 07:44:22 2017
New Revision: 1016727

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.7.1-enable-authenticated-users-to-browse-and-read-entries.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Aug 13 07:44:22 2017
@@ -1 +1 @@
-1803383
+1804881

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 Aug 13 07:44:22 2017
@@ -186,6 +186,11 @@ h2:hover > .headerlink, h3:hover > .head
 <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">&para;</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>
+<DIV class="warning" markdown="1">
+<B>Reminder...</B>
+Don't't forget to check the 'fetch subentries' and 'fetch operational attributes' in your connection's browser option tab, otherwise some parts of the following tutorial will not appear !
+</DIV>
+
 <h2 id="administrationpoint-setup">AdministrationPoint setup<a class="headerlink" href="#administrationpoint-setup" title="Permanent link">&para;</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>