[
https://issues.apache.org/jira/browse/HDFS-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847776#comment-13847776
]
Benoy Antony commented on HDFS-5660:
------------------------------------
I can get HDFS SSL work using dfs.https.enable and 3 additional configs ( NN
port , DN port and keystore config.)
With this scheme, two ports on NN and each data node will be opened. These
additional ports will not be used in our case.
I am doing all these steps just so that infosecurePort is set to 1006 which is
essentially what this patch does.
> When SSL is enabled , the Namenode WEBUI redirects to Infosecport, which
> could be 0
> -----------------------------------------------------------------------------------
>
> Key: HDFS-5660
> URL: https://issues.apache.org/jira/browse/HDFS-5660
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.2.0
> Reporter: Benoy Antony
> Assignee: Benoy Antony
> Attachments: HDFS-5660.patch
>
>
> (case 1) When SSL is enabled by setting "hadoop.ssl.enabled", SSL will be
> enabled on the regular port (infoport) on Datanode.
> (case 2) When SSL on HDFS is enabled by setting "dfs.https.enable", SSL will
> be enabled on a separate port (infoSecurePort) on Datanode.
> if SSL is enabled , the Namenode always redirects to infoSecurePort.
> "infoSecurePort" will be 0 in case 1 above.
> This breaks the file browsing via web.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
