You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Jakob Homan (JIRA)" <ji...@apache.org> on 2010/02/01 04:59:51 UTC

[jira] Updated: (HADOOP-6299) Use JAAS LoginContext for our login

     [ https://issues.apache.org/jira/browse/HADOOP-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jakob Homan updated HADOOP-6299:
--------------------------------

    Attachment: HADOOP-6299-Y20.patch

Patch for Yahoo!'s distribution. Tests and test-patch are fine (except known issue HADOOP-6530).

> 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, h-6299.patch, h-6299.patch, h-6299.patch, h-6299.patch, HADOOP-6299-2.patch, HADOOP-6299-Y20.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.