You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Mit Desai (JIRA)" <ji...@apache.org> on 2014/04/14 16:13:16 UTC

[jira] [Commented] (HDFS-4587) Webhdfs secure clients are incompatible with non-secure NN

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

Mit Desai commented on HDFS-4587:
---------------------------------

As 0.23 is going into the maintenance state and this bug will not be fixed in it, I am removing the target version for 0.23.11

> Webhdfs secure clients are incompatible with non-secure NN
> ----------------------------------------------------------
>
>                 Key: HDFS-4587
>                 URL: https://issues.apache.org/jira/browse/HDFS-4587
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode, webhdfs
>    Affects Versions: 3.0.0, 0.23.7, 2.0.4-alpha
>            Reporter: Daryn Sharp
>
> A secure webhdfs client will receive an exception from a non-secure NN.  For a NN in non-secure mode, {{FSNamesystem#getDelegationToken}} will return "null" to indicate no token is required.  Hdfs will send back the null to the client, but webhdfs uses {{DelegationTokenSecretManager.createCredentials}} which instead throws an exception.



--
This message was sent by Atlassian JIRA
(v6.2#6252)