You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by bu...@apache.org on 2014/03/17 13:00:35 UTC

svn commit: r901969 - in /websites/staging/isis/trunk: cgi-bin/ content/ content/components/security/shiro/using-ldap.html

Author: buildbot
Date: Mon Mar 17 12:00:34 2014
New Revision: 901969

Log:
Staging update by buildbot for isis

Modified:
    websites/staging/isis/trunk/cgi-bin/   (props changed)
    websites/staging/isis/trunk/content/   (props changed)
    websites/staging/isis/trunk/content/components/security/shiro/using-ldap.html

Propchange: websites/staging/isis/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Mar 17 12:00:34 2014
@@ -1 +1 @@
-1578298
+1578324

Propchange: websites/staging/isis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Mar 17 12:00:34 2014
@@ -1 +1 @@
-1578298
+1578324

Modified: websites/staging/isis/trunk/content/components/security/shiro/using-ldap.html
==============================================================================
--- websites/staging/isis/trunk/content/components/security/shiro/using-ldap.html (original)
+++ websites/staging/isis/trunk/content/components/security/shiro/using-ldap.html Mon Mar 17 12:00:34 2014
@@ -382,6 +382,24 @@ securityManager.realms = $ldapRealm
 
 <p>The above configuration has been tested against <a href="http://directory.apache.org/apacheds/">ApacheDS</a>, v1.5.7.  This can be administered using <a href="http://directory.apache.org/studio/">Apache Directory Studio</a>, v1.5.3.</p>
 
+<h3>Using a shared role/perms path</h3>
+
+<p>As an alternative to injecting the <code>permissionsByRole</code> property, the role/permission mapping can alternatively be specified by injecting a resource path:</p>
+
+<pre><code>ldapRealm.resourcePath=classpath:webapp/myroles.ini
+</code></pre>
+
+<p>where <code>myroles.ini</code> is in <code>src/main/resources/webapp</code>, and takes the form:</p>
+
+<pre><code> [roles]
+ user_role = *:ToDoItemsJdo:*:*,\
+             *:ToDoItem:*:*
+ self-install_role = *:ToDoItemsFixturesService:install:*
+ admin_role = *
+</code></pre>
+
+<p>This separation of the role/mapping can be useful if Shiro is configured to support multiple realms (eg an LdapRealm based one and also an TextRealm)</p>
+
 <h3>Active DS LDAP Configuration</h3>
 
 <p>The screenshot below shows the ApacheDS using Apache Directory Studio.  The setup here was initially base on <a href="http://krams915.blogspot.co.uk/2011/01/ldap-apache-directory-studio-basic.html">this tutorial</a>.  However, user accounts have been moved to a separate node.</p>