Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Thu, 27 Sep 2012 15:01:10 +1100 (NCT)
From: "Eli Collins (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <1864393031.131910.1348718470513.JavaMail.jiratomcat@arcas>
Subject: [jira] [Created] (HDFS-3983) Hftp should not use the https port
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Eli Collins created HDFS-3983:
---------------------------------

             Summary: Hftp should not use the https port
                 Key: HDFS-3983
                 URL: https://issues.apache.org/jira/browse/HDFS-3983
             Project: Hadoop HDFS
          Issue Type: Bug
    Affects Versions: 2.0.0-alpha
            Reporter: Eli Collins


Hftp currently doesn't work against a secure cluster unless you configure {{dfs.https.port}} to be the http port, otherwise the client can't fetch tokens:

{noformat}
$ hadoop fs -ls hftp://c1225.hal.cloudera.com:50070/
12/09/26 18:02:00 INFO fs.FileSystem: Couldn't get a delegation token from http://c1225.hal.cloudera.com:50470 using http.
ls: Security enabled but user not authenticated by filter
{noformat}

This is due to Hftp still using the https port. Post HDFS-2617 it should use the regular http port. Hsftp should still use the secure port, however now that we have HADOOP-8581 it's worth considering removing Hsftp entirely. I'll start a separate thread about that.  


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