[
https://issues.apache.org/jira/browse/YARN-3053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838885#comment-15838885
]
Jian He commented on YARN-3053:
-------------------------------
bq. Because for such clients we will not have a mechanism to pass the token
when collector/NM restarts.
sorry, didn't get that. For such apps, won't the client still need to pass the
new address to the AMs in app's own way. IIUC, it has no difference with
passing the token.
Also, I'm not sure the original collector design had accounted for unmanaged AM
in general case. (I think the collector is not even launched currently for
unmanaged AM). A lot other details need to be freshed out.
> [Security] Review and implement authentication in ATS v.2
> ---------------------------------------------------------
>
> Key: YARN-3053
> URL: https://issues.apache.org/jira/browse/YARN-3053
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Sangjin Lee
> Assignee: Varun Saxena
> Labels: YARN-5355, yarn-5355-merge-blocker
> Attachments: ATSv2Authentication(draft).pdf
>
>
> Per design in YARN-2928, we want to evaluate and review the system for
> security, and ensure proper security in the system.
> This includes proper authentication, token management, access control, and
> any other relevant security aspects.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
