You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by bu...@apache.org on 2014/09/14 10:19:09 UTC
svn commit: r922131 - in /websites/staging/sling/trunk/content: ./
documentation/bundles/resource-access-security.html
Author: buildbot
Date: Sun Sep 14 08:19:09 2014
New Revision: 922131
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/bundles/resource-access-security.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Sep 14 08:19:09 2014
@@ -1 +1 @@
-1624630
+1624806
Modified: websites/staging/sling/trunk/content/documentation/bundles/resource-access-security.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/bundles/resource-access-security.html (original)
+++ websites/staging/sling/trunk/content/documentation/bundles/resource-access-security.html Sun Sep 14 08:19:09 2014
@@ -148,7 +148,8 @@
</pre></div>
-<p>And you have to register the ResourceAccessGate with the path where you wanât to restrict access and the operation property set to âreadâ. Furthermore you have to decide if the ResourceAccessGate should operate on all resource providers (context=âapplicationâ) or only on the resourceproviders flagged with the property useResourceAccessSecurity=true (context=âproviderâ).</p>
+<p>And you have to register the ResourceAccessGate with the path where you wanât to restrict access and the operation property set to âreadâ. Furthermore you have to decide if the ResourceAccessGate should operate on all resource providers (context=âapplicationâ) or only on the resourceproviders flagged with the property useResourceAccessSecurity=true (context=âproviderâ).
+Tipp: We do not recommend to mix up application and provider context in the same application. This can lead to confusing configurations in the ResourceAccessGate implementations.</p>
<h3 id="gateresult">GateResult</h3>
<p>GateResult does have three states:</p>
<ul>
@@ -160,7 +161,7 @@
<h2 id="actual-state-of-resourceaccesssecurity">Actual state of ResourceAccessSecurity</h2>
<p>By now the implementation is complete for securing access on resource level for CRUD operations. It is not yet ready to allow fine granular access rights on values of a resource. So at the moment the <code>canReadValue, canUpdateValue, canDeleteValue</code> and <code>canCreateValue</code> on <code>ResourceAccessGate</code> methods are ignored.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1581277 by mykee on Tue, 25 Mar 2014 08:39:42 +0000
+ Rev. 1624806 by mykee on Sun, 14 Sep 2014 08:18:54 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project