hadoop-hdfs-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] (HDFS-4542) Webhdfs doesn't support secure proxy users
Date Fri, 01 Mar 2013 21:37:12 GMT

    [ https://issues.apache.org/jira/browse/HDFS-4542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590961#comment-13590961
] 

Hadoop QA commented on HDFS-4542:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12571649/HDFS-4542.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 tests included appear to have a timeout.{color}

    {color:red}-1 javac{color:red}.  The patch appears to cause the build to fail.

Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4027//console

This message is automatically generated.
                
> Webhdfs doesn't support secure proxy users
> ------------------------------------------
>
>                 Key: HDFS-4542
>                 URL: https://issues.apache.org/jira/browse/HDFS-4542
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: webhdfs
>    Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>         Attachments: HDFS-4542.patch
>
>
> Webhdfs doesn't ever send the {{DoAsParam}} in the REST calls for proxy users.  Proxy
users on a non-secure cluster "work" because the server sees them as the effective user, not
a proxy user, which effectively bypasses the proxy authorization checks.  On secure clusters,
it doesn't work at all in part due to wrong ugi being used for the connection (HDFS-3367),
but then it fails because the effective user tries to use a non-proxy token for the real user.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message