[
https://issues.apache.org/jira/browse/SHIRO-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417985#comment-15417985
]
Kusmanjali commented on SHIRO-579:
----------------------------------
Below list of filter chain works as expected for the URL
"example.appspot.com/_ah/api/hello/v1/first/second/third". The access is
granted for a user with permission X:create and not with Y:create.
addFilterChain("/*/first/second/*", AUTHC_BASIC, config(PERMS, "X:create"));
addFilterChain("/*/first/*", AUTHC_BASIC, config(PERMS, "Y:create"));
addFilterChain("/*/XYZ/*", AUTHC_BASIC, config(PERMS, "Z"));
> Permission filter is validating last matched path
> -------------------------------------------------
>
> Key: SHIRO-579
> URL: https://issues.apache.org/jira/browse/SHIRO-579
> Project: Shiro
> Issue Type: Bug
> Components: Integration: Guice
> Affects Versions: 1.3.0
> Environment: Google App Engine
> Reporter: Kusmanjali
> Assignee: Jared Bunting
> Priority: Blocker
>
> Following filter chain is present in configureShiroWeb() function
> addFilterChain("/**/first/second/**", AUTHC_BASIC, config(PERMS, "X:create"));
> addFilterChain("/**/first/**", AUTHC_BASIC, config(PERMS, "Y:create"));
> for a URL : example.appspot.com/_ah/api/hello/v1/first/second/third the
> access is granted for a user with permission Y:create and not with X:create.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
