You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Junping Du (JIRA)" <ji...@apache.org> on 2015/03/27 23:58:53 UTC

[jira] [Commented] (YARN-3402) Security support for new timeline service.

    [ https://issues.apache.org/jira/browse/YARN-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14384849#comment-14384849 ] 

Junping Du commented on YARN-3402:
----------------------------------

Thanks [~vinodkv] for reminding on this. Mark it unassigned which is practice for duplicated JIRA. 

> Security support for new timeline service.
> ------------------------------------------
>
>                 Key: YARN-3402
>                 URL: https://issues.apache.org/jira/browse/YARN-3402
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Junping Du
>            Assignee: Junping Du
>
> We should support YARN security for new TimelineService.
> Basically, there should be security token exchange between AM, NMs and app-collectors to prevent anyone who knows the service address of app-collector can post faked/unwanted information. Also, there should be tokens exchange between app-collector/RMTimelineCollector and backend storage (HBase, Phoenix, etc.) that enabling security.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)