From yarn-issues-return-141083-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Fri Mar 30 03:02:09 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 C63A1180645 for ; Fri, 30 Mar 2018 03:02:08 +0200 (CEST) Received: (qmail 71520 invoked by uid 500); 30 Mar 2018 01:02:02 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 71504 invoked by uid 99); 30 Mar 2018 01:02:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Mar 2018 01:02:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 67F9EC7121 for ; Fri, 30 Mar 2018 01:02:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id x-wbltB-1MjS for ; Fri, 30 Mar 2018 01:02:02 +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 B0D695FB4C for ; Fri, 30 Mar 2018 01:02: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 286D5E0E70 for ; Fri, 30 Mar 2018 01:02:01 +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 43BC3255F9 for ; Fri, 30 Mar 2018 01:02:00 +0000 (UTC) Date: Fri, 30 Mar 2018 01:02:00 +0000 (UTC) From: "Wangda Tan (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-8091) Revisit checkUserAccessToQueue RM REST API 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/YARN-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420019#comment-16420019 ] Wangda Tan commented on YARN-8091: ---------------------------------- 1) If login user isn't allowed to access the queue info (who doesn't have admin permission of the queue), 403 will be thrown. 2) If login user is allowed, we will return an object: {code} {"allowed":"true","user":"root1","diagnostics":""} {code} > Revisit checkUserAccessToQueue RM REST API > ------------------------------------------ > > Key: YARN-8091 > URL: https://issues.apache.org/jira/browse/YARN-8091 > Project: Hadoop YARN > Issue Type: Task > Reporter: Wangda Tan > Assignee: Wangda Tan > Priority: Critical > > As offline suggested by [~sershe]. Currently design of the checkUserAccessToQueue mixed config-related issues (like user doesn't access to the URL) and user-facing output (like requested user is not permitted to access the queue) in the same code. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org