hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hairong Kuang (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-2229) Provide a simple login implementation
Date Wed, 28 Nov 2007 19:04:43 GMT

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

Hairong Kuang updated HADOOP-2229:

    Attachment: ugi1.patch

On the second thought, I feel that getUMask() should not be part of the UserGroupInformation
(UGI) interface. One reason is that umask is not needed on the server side and it does not
need to be transferred over the wire. In the new method, I removed getUMask from UGI, but
UnixUserGroupInformation still implements this method and umask gets saved into configuration.

> Provide a simple login implementation
> -------------------------------------
>                 Key: HADOOP-2229
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2229
>             Project: Hadoop
>          Issue Type: New Feature
>    Affects Versions: 0.15.0
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Hairong Kuang
>             Fix For: 0.16.0
>         Attachments: ugi.patch, ugi1.patch
> Give a simple implementation of HADOOP-1701.    Hadoop clients are assumed to be started
within a Unix-like network which provides user and group management.  This implementation
read user information from the OS and send them to the NameNode in plaintexts through RPC
(see also HADOOP-2184).  NameNode trusts all information given and uses them for permission

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message