You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/10/16 15:39:46 UTC

[jira] [Commented] (WW-4117) RolesInterceptor ignores disallowedRoles when allowedRoles are configured

    [ https://issues.apache.org/jira/browse/WW-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796789#comment-13796789 ] 

ASF subversion and git services commented on WW-4117:
-----------------------------------------------------

Commit 1532760 from [~lukaszlenart] in branch 'struts2/trunk'
[ https://svn.apache.org/r1532760 ]

WW-4117 Makes fields protected instead of private to meet user's needs

> RolesInterceptor ignores disallowedRoles when allowedRoles are configured
> -------------------------------------------------------------------------
>
>                 Key: WW-4117
>                 URL: https://issues.apache.org/jira/browse/WW-4117
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Core Interceptors
>            Reporter: Cam Morris
>             Fix For: 2.3.16
>
>         Attachments: patch.txt
>
>
> The isAllowed method of RolesInterceptor does not enforce the disallowedRoles when allowedRoles are configured.  ex:
> {code}    
> <interceptor-ref name="roles">
>   <param name="allowedRoles">authenticated</param>
>   <param name="disallowedRoles">restrictedUser</param>
> </interceptor-ref>
> {code}
> With the above configuration a user with the roles "authenticated", and "restrictedUser" would be granted access.



--
This message was sent by Atlassian JIRA
(v6.1#6144)