hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-2528) webhdfs rest call to a secure dn fails when a token is sent
Date Wed, 11 Jan 2012 05:56:40 GMT

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

Eli Collins updated HDFS-2528:

    Target Version/s:   (was: 1.0.0)
       Fix Version/s:     (was: 1.1.0)
                          (was: 0.23.0)

This was included in branch-23.0 but not shipped as part of the 23.0 release.
> webhdfs rest call to a secure dn fails when a token is sent
> -----------------------------------------------------------
>                 Key: HDFS-2528
>                 URL: https://issues.apache.org/jira/browse/HDFS-2528
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>    Affects Versions:
>            Reporter: Arpit Gupta
>            Assignee: Tsz Wo (Nicholas), SZE
>             Fix For: 0.24.0, 0.23.1, 1.0.0
>         Attachments: h2528_20111101.patch, h2528_20111101_0.20s.patch, h2528_20111101b.patch,
h2528_20111101b_0.20s.patch, h2528_20111102.patch, h2528_20111102_0.20s.patch, h2528_20111103.patch,
h2528_20111103_0.20s.patch, h2528_20111103_0.20s.patch
> curl -L -u : --negotiate -i "http://NN:50070/webhdfs/v1/tmp/webhdfs_data/file_small_data.txt?op=OPEN"
> the following exception is thrown by the datanode when the redirect happens.
> {"RemoteException":{"exception":"IOException","javaClassName":"java.io.IOException","message":"Call
to  failed on local exception: java.io.IOException: javax.security.sasl.SaslException: GSS
initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed
to find any Kerberos tgt)]"}}
> Interestingly when using ./bin/hadoop with a webhdfs path we are able to cat or tail
a file successfully.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message