From yarn-issues-return-117974-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org Thu Jul 20 06:07:09 2017 Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0E30E19E5A for ; Thu, 20 Jul 2017 06:07:09 +0000 (UTC) Received: (qmail 18520 invoked by uid 500); 20 Jul 2017 06:07:03 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 18478 invoked by uid 500); 20 Jul 2017 06:07:03 -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 18467 invoked by uid 99); 20 Jul 2017 06:07:03 -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; Thu, 20 Jul 2017 06:07:03 +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 29CBD1A1B24 for ; Thu, 20 Jul 2017 06:07:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id DkfNMyl_5dFZ for ; Thu, 20 Jul 2017 06:07: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 2BC945F2F1 for ; Thu, 20 Jul 2017 06:07:02 +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 0392AE0DFC for ; Thu, 20 Jul 2017 06:07: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 28FFE21ECF for ; Thu, 20 Jul 2017 06:07:00 +0000 (UTC) Date: Thu, 20 Jul 2017 06:07:00 +0000 (UTC) From: "Vrushali C (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-6820) Restrict read access to timelineservice v2 data MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-6820?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16094= 243#comment-16094243 ]=20 Vrushali C commented on YARN-6820: ---------------------------------- Adding to what I mentioned above. If a user=E2=80=99s labels do not match a cell=E2=80=99s label or expressio= n, the user will be denied access to the cell. The timeline service scan wi= ll be done as "ats" user. Say the "ats" user is a super user / admin in hba= se. So "ats" user has access to all tables.=20 We can specify a different authorization during the Scan or Get, by passing= the AUTHORIZATIONS option in HBase Shell, or the setAuthorizations() metho= d in the API. This authorization will be combined with the default set as a= n additional filter. It will further filter the results.=20 So say group "tez-admins" is the label applied to the cell while writing. N= ow if a user queries the rest api of timeline service and that user is part= of "tez-admins" group, then this authorization should return the cells.=20 If another user say "search-admin" is querying the rest api of timeline ser= vice and that "search-admin" is *not* part of "tez-admins" group, then this= hbase visibility filtering / authorization should *NOT* return the cells.= =20 I need to test this, we currently don't have any auth or visibility set on = our hbase clusters. Will see what I can do.=20 > Restrict read access to timelineservice v2 data=20 > ------------------------------------------------ > > Key: YARN-6820 > URL: https://issues.apache.org/jira/browse/YARN-6820 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver > Reporter: Vrushali C > Labels: yarn-5355-merge-blocker > > Need to provide a way to restrict read access in ATSv2. Not all users sho= uld be able to read all entities. On the flip side, some folks may not need= any read restrictions, so we need to provide a way to disable this access = restriction as well.=20 > Initially this access restriction could be done in a simple way via a whi= telist of users allowed to read data. That set of users can read all data, = no other user can read any data. Can be turned off for all users to read al= l data. > Could be stored in a "domain" table in hbase perhaps. Or a configuration = setting for the cluster. Or something else that's simple enough. ATSv1 has = a concept of domain for isolating users for reading. Would be good to keep = that in consideration.=20 > In ATSv1, domain offers a namespace for Timeline server allowing users to= host multiple entities, isolating them from other users and applications. = A =E2=80=9CDomain=E2=80=9D in ATSV1 primarily stores owner info, read and& = write ACL information, created and modified time stamp information. Each Do= main is identified by an ID which must be unique across all users in the YA= RN cluster. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org