[
https://issues.apache.org/jira/browse/YARN-3053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15832407#comment-15832407
]
Jason Lowe commented on YARN-3053:
----------------------------------
Sorry to jump in relatively late on this. A couple of questions came up while
looking over the document.
# For things like Slider and other long-running services, there's going to be a
need to regenerate the ATS token (i.e.: token rolling similar to what is
already done for other YARN tokens). It would be good to have the strategy for
that explained.
# How are unmanaged AMs handled? Do they have a collector, how do they
authenticate, etc.?
# How are entites that are _not_ AMs handled? For example, what if a service
outside of YARN wants to post ATS events? Do they have a collector, how do
they authenticate, etc.?
> [Security] Review and implement security 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: [email protected]
For additional commands, e-mail: [email protected]
