svn commit: r1000690 - in /websites/staging/jena/trunk/content: ./ documentation/fuseki2/fuseki-security.html

[bu...@apache.org]

Author: buildbot
Date: Mon Nov  7 22:06:45 2016
New Revision: 1000690

Log:
Staging update by buildbot for jena

Modified:
    websites/staging/jena/trunk/content/   (props changed)
    websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-security.html

Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Nov  7 22:06:45 2016
@@ -1 +1 @@
-1768597
+1768598

Modified: websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-security.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-security.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-security.html Mon Nov  7 22:06:45 2016
@@ -166,12 +166,17 @@ actions are limited to the localhost. "l
 connecting using the <code>http://localhost:.../...</code>. It must be "localhost", or
 <code>127.0.0.1</code> (IPv4), or <code>[::1]</code> (IPv6), not the external IP address of the
 machine.</p>
+<p>Once shiro has been configured to perform user authentication it provides 
+a good foundation on which to implement the <a href="../permissions/">Jena Permissions</a>
+layer.  There is an <a href="../permissions/example.html">example implementation</a> 
+documented in the Jena Permissions section.  The Jena Permissions layer can 
+be used to restrict access to specific graphs or triples within graphs.</p>
 <p>There is an example to enable simple user/password security; this is only
 suitable where the connection is secure, is shown <code>shiro.ini</code> file with
 defaults user 'admin' and password 'pw'.  These should be changed before
 use.</p>
 <p>This has some use where the server is in a secure network environment with
-additional restrictions on extenral requests also applied.  behind a
+additional restrictions on external requests also applied.  behind a
 reverse proxy and the connection can have addition security (e.g. no access
 to URLs starting '/$/').</p>
 <p>The Apache Shiro website has documentation for creating more sophisticated