hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12953) New API for libhdfs to get FileSystem object as a proxy user
Date Tue, 22 Mar 2016 20:24:25 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-12953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207216#comment-15207216

Hadoop QA commented on HADOOP-12953:

| (x) *{color:red}-1 overall{color}* |
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s {color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 13s {color} | {color:red}
HADOOP-12953 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute
for help. {color} |
|| Subsystem || Report/Notes ||
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12794826/HADOOP-12953.001.patch
| JIRA Issue | HADOOP-12953 |
| Console output | https://builds.apache.org/job/PreCommit-HADOOP-Build/8895/console |
| Powered by | Apache Yetus 0.2.0   http://yetus.apache.org |

This message was automatically generated.

> New API for libhdfs to get FileSystem object as a proxy user
> ------------------------------------------------------------
>                 Key: HADOOP-12953
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12953
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>            Reporter: Uday Kale
>            Assignee: Uday Kale
>         Attachments: HADOOP-12953.001.patch
> Secure impersonation in HDFS needs users to create proxy users and work with those. In
libhdfs, the hdfsBuilder accepts a userName but calls FileSytem.get() or FileSystem.newInstance()
with the user name to connect as. But, both these interfaces use getBestUGI() to get the UGI
for the given user. This is not necessarily true for all services whose end-users would not
access HDFS directly, but go via the service to first get authenticated with LDAP, then the
service owner can impersonate the end-user to eventually provide the underlying data.
> For such services that authenticate end-users via LDAP, the end users are not authenticated
by Kerberos, so their authentication details wont be in the Kerberos ticket cache. HADOOP_PROXY_USER
is not a thread-safe way to get this either. 
> Hence the need for the new API for libhdfs to get the FileSystem object as a proxy user
using the 'secure impersonation' recommendations. This approach is  secure since HDFS authenticates
the service owner and then validates the right for the service owner to impersonate the given
user as allowed by hadoop.proxyusers.* parameters of HDFS config.

This message was sent by Atlassian JIRA

View raw message