You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Cam Morris (JIRA)" <ji...@apache.org> on 2013/06/19 18:25:20 UTC
[jira] [Commented] (WW-4118) Allow RolesInterceptor to validate
role names
[ https://issues.apache.org/jira/browse/WW-4118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688122#comment-13688122 ]
Cam Morris commented on WW-4118:
--------------------------------
Attached to WW-4117 is a patch that implements this improvement and adds unit tests for this feature. It includes an override-able boolean areRolesValid(List<String> roles) that is called by setAllowedRoles and setDisallowedRoles.
> Allow RolesInterceptor to validate role names
> ---------------------------------------------
>
> Key: WW-4118
> URL: https://issues.apache.org/jira/browse/WW-4118
> Project: Struts 2
> Issue Type: Improvement
> Reporter: Cam Morris
> Priority: Minor
>
> Role names can be easily misconfigured resulting in security holes. However app developers typically known which roles are available in their environment. A small tweak to RolesInterceptor could make it easy for developers to have role verification. When the roles are invalid the RolesInterceptor could fail-fast, quickly bringing the issue to attention.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira