From yarn-dev-return-29615-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Mon Feb 12 23:08:05 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id E3EA2180652 for ; Mon, 12 Feb 2018 23:08:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id D3A63160C63; Mon, 12 Feb 2018 22:08:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 29E6B160C61 for ; Mon, 12 Feb 2018 23:08:05 +0100 (CET) Received: (qmail 50302 invoked by uid 500); 12 Feb 2018 22:08:04 -0000 Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-dev@hadoop.apache.org Received: (qmail 50158 invoked by uid 99); 12 Feb 2018 22:08:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Feb 2018 22:08:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 90C801A0B65 for ; Mon, 12 Feb 2018 22:08:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -102.311 X-Spam-Level: X-Spam-Status: No, score=-102.311 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id kHGPej3SAGqR for ; Mon, 12 Feb 2018 22:08:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 9BCF75FAC6 for ; Mon, 12 Feb 2018 22:08:01 +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 D621FE01BE for ; Mon, 12 Feb 2018 22:08:00 +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 64447240FA for ; Mon, 12 Feb 2018 22:08:00 +0000 (UTC) Date: Mon, 12 Feb 2018 22:08:00 +0000 (UTC) From: "Eric Yang (JIRA)" To: yarn-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (YARN-7923) Refine proxy user authorization to support multiple ACL list MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Eric Yang created YARN-7923: ------------------------------- Summary: Refine proxy user authorization to support multiple A= CL list Key: YARN-7923 URL: https://issues.apache.org/jira/browse/YARN-7923 Project: Hadoop YARN Issue Type: Bug Components: security Affects Versions: 3.0.0 Reporter: Eric Yang Assignee: Eric Yang This Jira is responding to follow up work for HADOOP-14077.=C2=A0 The origi= nal goal of HADOOP-14077 is to have ability to support multiple ACL lists.= =C2=A0 When checking for proxy user authorization in AuthenticationFilter t= o ensure there is a way to authorize normal users and admin users using sep= arate proxy users ACL lists.=C2=A0 This was suggested in [HADOOP-14060|http= s://issues.apache.org/jira/browse/HADOOP-14060?focusedCommentId=3D15875737&= page=3Dcom.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#c= omment-15875737] to configure AuthenticationFilterWithProxyUser this way: AuthenticationFilterWithProxyUser->StaticUserWebFilter->AuthenticationFIlte= rWithProxyUser This enables the second AuthenticationFilterWithProxyUser validates both cr= edentials claim by proxy user, and end user. However, there is a side effect that unauthorized users are not properly re= jected with 403 FORBIDDEN message if there is no other web filter configure= d to handle the required authorization work. This JIRA is intend to discuss the work of HADOOP-14077 by either combine S= taticUserWebFilter + second AuthenticationFilterWithProxyUser into a Author= izationFilterWithProxyUser as a final filter to evict unauthorized user, or= revert both HADOOP-14077 and HADOOP-13119 to eliminate the false positive = in user authorization. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-dev-help@hadoop.apache.org