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

Hudson commented on HDFS-4560:
------------------------------

Integrated in Hadoop-Mapreduce-trunk #1366 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1366/])
    HDFS-4560. Webhdfs cannot use tokens obtained by another user (daryn) 
(Revision 1453955)

     Result = SUCCESS
daryn : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1453955
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/web/WebHdfsFileSystem.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/web/TestWebHdfsUrl.java

                
> Webhdfs cannot use tokens obtained by another user
> --------------------------------------------------
>
>                 Key: HDFS-4560
>                 URL: https://issues.apache.org/jira/browse/HDFS-4560
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: webhdfs
>    Affects Versions: 3.0.0, 0.23.7, 2.0.5-beta
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>             Fix For: 3.0.0, 0.23.7, 2.0.4-alpha
>
>         Attachments: HDFS-4560.patch, HDFS-4560.patch
>
>
> Webhdfs passes {{UserParam}} even when a token is being used.  The NN will 
> construct the UGI from the token and error if the {{UserParam}} does not 
> match the token's.  This causes problems when a token for user A is used with 
> user B's context.  This is in contrast to hdfs which will honor the token's 
> ugi no matter the client's current context.  The passing of a token or user 
> params should be mutually exclusive.

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

Reply via email to