[
https://issues.apache.org/jira/browse/HADOOP-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653267#action_12653267
]
Steve Loughran commented on HADOOP-4490:
----------------------------------------
You are about to take on one of the big problems they hit in the grid world:
identity. all the grid tools (condor, platform, etc) have lots of effort put in
at the OS level to create new users on target machines, manage the disk and cpu
usage limits of that user, etc. But you also need to propagate identity over
the wire, which gets you into SAML and other things. Because right now the
JobTracker trusts you to be who you say you are -having caller authentication
would be a prerequisite to doing back-end user switching.
If you are interested in running pure Java apps under different rights, this
could be done via a security manager. Every task would be started with an
explicit security manager/policy that limited what it could do, file and
network operations would be checked against the policy. This would be portable
and easier to test. It also eliminates the need to run the TT as root, to keep
the unix user database in sync with the hadoop user list, etc.
> Map and Reduce tasks should run as the user who submitted the job
> -----------------------------------------------------------------
>
> Key: HADOOP-4490
> URL: https://issues.apache.org/jira/browse/HADOOP-4490
> Project: Hadoop Core
> Issue Type: Sub-task
> Components: mapred, security
> Reporter: Arun C Murthy
> Assignee: Hemanth Yamijala
>
> Currently the TaskTracker spawns the map/reduce tasks, resulting in them
> running as the user who started the TaskTracker.
> For security and accounting purposes the tasks should be run as the job-owner.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
