Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 20 Jul 2017 07:04:00 +0000 (UTC)
From: "Varun Saxena (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13086970.1499970767000.289515.1500534240098@Atlassian.JIRA>
In-Reply-To: <JIRA.13086970.1499970767000@Atlassian.JIRA>
References: <JIRA.13086970.1499970767000@Atlassian.JIRA> <JIRA.13086970.1499970767259@jira-lw-us.apache.org>
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
archived-at: Thu, 20 Jul 2017 07:04:06 -0000


    [ https://issues.apache.org/jira/browse/YARN-6820?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16094=
275#comment-16094275 ]=20

Varun Saxena commented on YARN-6820:
------------------------------------

As all reads from Timeline Reader would be with ats user, so would specifyi=
ng authorizations/labels in the scan be sufficient to filter out the result=
s? If yes, we can utilize this for our eventual authorization solution, wit=
h user/groups/domain written as labels during put and specified as authoriz=
ation during get/scan.

By the way for whitelisting/blacklisting, for our next drop, a simple confi=
guration with a check in reader not suffice?

> 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