You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Kalle Korhonen (JIRA)" <ji...@apache.org> on 2010/06/25 21:52:50 UTC
[jira] Assigned: (SHIRO-175) Improve Set of permission and role
checks
[ https://issues.apache.org/jira/browse/SHIRO-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kalle Korhonen reassigned SHIRO-175:
------------------------------------
Assignee: Kalle Korhonen
> Improve Set of permission and role checks
> -----------------------------------------
>
> Key: SHIRO-175
> URL: https://issues.apache.org/jira/browse/SHIRO-175
> Project: Shiro
> Issue Type: Improvement
> Components: Authorization (access control)
> Reporter: Pierce Wetter
> Assignee: Kalle Korhonen
>
> Both the shiro tag library and tapestry-security have seen fit to extend the permissions and role checks. It would be nice to have a complete set of annotations and permissions checks as follows:
> Right now, Shiro supports:
> @RequiresRoles(String)
> @RequiresPermissions(String)
> These have the additionally issue that multiple values are separated by commas, which conflicts with commas in the permission strings.
> I would like to suggest the following more complete, and specific set:
> @RequiresAllRoles(String[] ) <-- same as current RequiresRoles, except the AND is specified, and the roles can be done via:
> @RequiresAllRoles( {"role1", "role2"} )
> @RequiresAnyRoles(String[] ) <--- the OR version, runs if any role is implied.
> @RequiresAllPermissions(String[] )
> @RequiresAnyPermissions(String[] )
> SecurityCheck(allRoles, anyRoles, allPermissions, anyPermissions) <--- all in one with one annotation
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.