Author: buildbot
Date: Wed Dec 11 02:29:17 2013
New Revision: 889925
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/bundles/web-console-extensions.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Dec 11 02:29:17 2013
@@ -1 +1 @@
-1550003
+1550031
Modified:
websites/staging/sling/trunk/content/documentation/bundles/web-console-extensions.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/bundles/web-console-extensions.html
(original)
+++
websites/staging/sling/trunk/content/documentation/bundles/web-console-extensions.html
Wed Dec 11 02:29:17 2013
@@ -91,6 +91,7 @@
<li><a href="#branding-orgapacheslingextensionswebconsolebranding">Branding
(org.apache.sling.extensions.webconsolebranding)</a></li>
<li><a
href="#security-provider-orgapacheslingextensionswebconsolesecurityprovider">Security
Provider (org.apache.sling.extensions.webconsolesecurityprovider)</a><ul>
<li><a href="#configuration">Configuration</a></li>
+<li><a href="#authentication-handling">Authentication Handling</a></li>
</ul>
</li>
</ul>
@@ -99,7 +100,7 @@
<p>The Apache Sling Web Console Branding provided by Apache Sling is currently
just for the product logo displayed in the upper right corner of the Web
Console and some titles and strings.</p>
<p>This bundle will attach as a fragment bundle to the Apache Felix Web
Console bundle. To enable it after installation into a running system, you
might have to refresh the package imports of the Apache Felix Web Console
bundle. If you install using the Apache Felix Web Console bundle installation
functionality, this will be taken care of by the Web Console.</p>
<h2
id="security-provider-orgapacheslingextensionswebconsolesecurityprovider">Security
Provider (org.apache.sling.extensions.webconsolesecurityprovider)</h2>
-<p>The Apache Sling Web Console Security Provider implements the Apache Felix
Web Console <code>WebConsoleSecurityProvider</code> interface authenticating
Web Console users against the JCR repository. Each username and password
presented is used to login to the JCR repository and to check the respective
session.</p>
+<p>The Apache Sling Web Console Security Provider implements the Apache Felix
Web Console <code>WebConsoleSecurityProvider</code> and
<code>WebConsoleSecurityProvider2</code> interface for authenticating Web
Console users against the JCR repository. Each username and password presented
is used to login to the JCR repository and to check the respective session.</p>
<ol>
<li>Ensure the username and password can be used to login to the default
workspace. If not, access is denied</li>
<li>If the username presented is one of the user names configured with the
<code>users</code> configuration property, access is granted.</li>
@@ -107,7 +108,7 @@
</ol>
<p>Access is denied if the username and password cannot be used to login to
the default workspace or if the user is neither one of the configured allowed
users nor in any of the configured groups.</p>
<h3 id="configuration">Configuration</h3>
-<p>The Security Provider is configured with configuration with PID
<code>org.apache.sling.extensions.webconsolesecurityprovider.internal.SlingWebConsoleSecurityProvider</code>
supporting the following properties:</p>
+<p>The Security Provider is configured with the configuration PID
<code>org.apache.sling.extensions.webconsolesecurityprovider.internal.SlingWebConsoleSecurityProvider</code>
supporting the following properties:</p>
<table>
<thead>
<tr>
@@ -130,8 +131,11 @@
</tbody>
</table>
<p>Note, that while the default value explicitly grants the <em>admin</em>
user to access the Web Console it is suggested that system administrators
define a special group and assign users with Web Console access to this
group.</p>
+<h3 id="authentication-handling">Authentication Handling</h3>
+<p>As long as the web console security provider bundle is not activate and has
not installed one of the above mentioned services, the default authentication
of the web console is used. Once the bundle is active and a JCR repository
service is available, the repository is used for authentication as explained
above. But still the login form of the web console is used which is usually
basic authentication.
+Once startup is finished and a Sling authentication service is available as
well, the security provider replaces the JCR repository based auth provider
with a Sling based auth provider. Both authenticate against the JCR repository,
however the Sling based one using Sling to render the login form. Therefore,
this provider is not registered until startup is finished</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1500501 by fmeschbe on Sun, 7 Jul 2013 18:49:51 +0000
+ Rev. 1550031 by cziegeler on Wed, 11 Dec 2013 02:29:05 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
