hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6299) Use JAAS LoginContext for our login
Date Fri, 22 Jan 2010 17:39:21 GMT

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

Owen O'Malley updated HADOOP-6299:
----------------------------------

    Attachment: h-6299.patch

This patch fixes:
  1. UGI.toString now just returns the user name.
  2. Fixes the javadoc warnings
  3. Adds more javadoc into UGI


> 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, 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.


Mime
View raw message