[
https://issues.apache.org/jira/browse/WW-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796805#comment-13796805
]
Hudson commented on WW-4117:
----------------------------
SUCCESS: Integrated in Struts2-JDK6 #811 (See
[https://builds.apache.org/job/Struts2-JDK6/811/])
WW-4117 Makes fields protected instead of private to meet user's needs
(lukaszlenart: rev 1532760)
*
/struts/struts2/trunk/core/src/main/java/org/apache/struts2/interceptor/RolesInterceptor.java
> 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
> Assignee: Lukasz Lenart
> 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)
