You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2013/08/19 03:07:48 UTC
[jira] [Updated] (SAMZA-19) Secure YARN AM
[ https://issues.apache.org/jira/browse/SAMZA-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Riccomini updated SAMZA-19:
---------------------------------
Affects Version/s: 0.6.0
> Secure YARN AM
> --------------
>
> Key: SAMZA-19
> URL: https://issues.apache.org/jira/browse/SAMZA-19
> Project: Samza
> Issue Type: Bug
> Affects Versions: 0.6.0
> Reporter: Chris Riccomini
> Assignee: Jakob Homan
>
> Samza's YARN AM starts a Jetty servlet container that runs a Scalatra/SCAML dashboard server for the Sama job, and a HTTP-RESTish RPC server on two different ports.
> We should secure the AM dashboard using Hadoop's security mechanism (a SPNEGO servlet filter, I believe).
> Need to investigate what to do regarding the RPC server.
> [~jakobhoman] Any feedback on the best approach here? Does SPNEGO filter seem sane? What's the pattern for RPC?
> I'm assuming MapReduce is using the same RPC as YARN, and get security at the RPC level for free.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira