[
https://issues.apache.org/jira/browse/HADOOP-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devaraj Das updated HADOOP-6299:
--------------------------------
Attachment: 6299-MR-early.patch
This patch fixes most of MR to do UGI stuff in the new model. This patch makes
MR compile on top of common built with the last patch Jakob uploaded. I didn't
attempt to run the tests yet. One reason is that I don't have the new hdfs test
class MiniHDFSCluster/DFSAdmin (and maybe others), and that's used in the MR
tests.
The other thing is the SecurityUtil's group mapping service is unavailable (and
a test depends on that). I believe Owen/Jakob are putting that in in the next
update to the patch for common.
This may be a good time to get rid of the JobContext.USER_NAME and its usage in
the framework. The patch doesn't address that.
And yes, moving MR to the new UGI model was messier than i initially expected.
> Use JAAS LoginContext for our login
> -----------------------------------
>
> Key: HADOOP-6299
> URL: https://issues.apache.org/jira/browse/HADOOP-6299
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Reporter: Arun C Murthy
> Assignee: Owen O'Malley
> Fix For: 0.22.0
>
> Attachments: 6299-MR-early.patch, h-6299.patch, HADOOP-6299-2.patch,
> UserGroupInformation.java, UserGroupInformation.java
>
>
> Currently we use a custom login module in UnixUserGroupInformation for
> acquiring user-credentials (via config or exec'ing 'whoami'). We should
> switch to using standard JAAS components such as LoginContext and possibly
> implement a custom UnixLoginContext for our current requirements. In future
> we can use this for Kerberos etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
