From dev-return-7628-archive-asf-public=cust-asf.ponee.io@shiro.apache.org Wed Feb 14 07:37:07 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id A0D8E180621 for ; Wed, 14 Feb 2018 07:37:06 +0100 (CET) Received: (qmail 78689 invoked by uid 500); 14 Feb 2018 06:37:05 -0000 Mailing-List: contact dev-help@shiro.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@shiro.apache.org Delivered-To: mailing list dev@shiro.apache.org Received: (qmail 78675 invoked by uid 99); 14 Feb 2018 06:37:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Feb 2018 06:37:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id E9A98C0024 for ; Wed, 14 Feb 2018 06:37:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id vQ9wpnlRlgLW for ; Wed, 14 Feb 2018 06:37:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id DFB6F5F1E7 for ; Wed, 14 Feb 2018 06:37:03 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id F21E6E0026 for ; Wed, 14 Feb 2018 06:37:02 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id B5A0C21E80 for ; Wed, 14 Feb 2018 06:37:01 +0000 (UTC) Date: Wed, 14 Feb 2018 06:37:00 +0000 (UTC) From: "Shilpi Das (JIRA)" To: dev@shiro.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (SHIRO-621) REST filter bypassing matched path MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SHIRO-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shilpi Das updated SHIRO-621: ----------------------------- Affects Version/s: 1.4.0 Description: The following filter chains are present in configureShiroWeb() function addFilterChain("/**/first/second/third/**", filterConfig(AUTHC_BASIC), filterConfig(REST, "X")); addFilterChain("/**/first/**", filterConfig(AUTHC_BASIC), filterConfig(REST, "Y")); When a request is made for an API- example.appspot.com/v1/first/second/third, the first filter is bypassed and the access is granted for a user with permission Y and not with X. I am using Shiro 1.4.0-RC2 version and Guice 3.0. I have also tried using Shiro 1.4.0 with Guice 4.0. was: The following filter chains are present in configureShiroWeb() function addFilterChain("/**/first/second/third/**", filterConfig(AUTHC_BASIC), filterConfig(REST, "X")); addFilterChain("/**/first/**", filterConfig(AUTHC_BASIC), filterConfig(REST, "Y")); When a request is made for an API- example.appspot.com/v1/first/second/third, the first filter is bypassed and the access is granted for a user with permission Y and not with X. I am using Shiro 1.4.0-RC2 version and Guice 3.0 > REST filter bypassing matched path > ---------------------------------- > > Key: SHIRO-621 > URL: https://issues.apache.org/jira/browse/SHIRO-621 > Project: Shiro > Issue Type: Bug > Components: Integration: Guice > Affects Versions: 1.4.0-RC2, 1.4.0 > Environment: Google App Engine > Reporter: Shilpi Das > Assignee: Jared Bunting > Priority: Major > > The following filter chains are present in configureShiroWeb() function > addFilterChain("/**/first/second/third/**", filterConfig(AUTHC_BASIC), filterConfig(REST, "X")); > addFilterChain("/**/first/**", filterConfig(AUTHC_BASIC), filterConfig(REST, "Y")); > When a request is made for an API- example.appspot.com/v1/first/second/third, the first filter is bypassed and the access is granted for a user with permission Y and not with X. > I am using Shiro 1.4.0-RC2 version and Guice 3.0. > I have also tried using Shiro 1.4.0 with Guice 4.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)