Also, if you are using the ModularRealmAuthorizer to aggregate your realms (and your Realms are AuthorizingRealms) You can set the RolePermissionResolver once: http://shiro.apache.org/static/1.2.1/apidocs/org/apache/shiro/authz/ModularRealmAuthorizer.html#setRolePermissionResolver(org.apache.shiro.authz.permission.RolePermissionResolver)
On Tue, Mar 10, 2015 at 11:30 AM, scSynergy <[email protected]> wrote: > In this example the author loads roles and their corresponding permissions > from MongoDB inside his custom made Shiro realm: > > http://shiro-user.582556.n2.nabble.com/Example-Shiro-MongoDB-Realm-td7579029.html > > Basically any Realm that extends AuthorizingRealm > (https://shiro.apache.org/static/1.2.3/apidocs/) has a method to set its > RolePermissionResolver. So, if you have all your realms extend > AuthorizingRealm and set the same RolePermissionResolver unto each of those > realms, then they should all behave alike. > > > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/How-to-predefine-a-role-permission-mapping-outside-realms-tp7580487p7580490.html > Sent from the Shiro User mailing list archive at Nabble.com. >
