Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Sat, 28 Sep 2013 00:12:03 +0000 (UTC)
From: "Jing Zhao (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12671054.1380326977013.33943.1380327123412@arcas>
In-Reply-To: <JIRA.12671054.1380326977013@arcas>
References: <JIRA.12671054.1380326977013@arcas>
Subject: [jira] [Updated] (HDFS-5273) Improve the documentation of
 SSL/HTTPS-related configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jing Zhao updated HDFS-5273:
----------------------------

    Priority: Major  (was: Minor)
    
> Improve the documentation of SSL/HTTPS-related configuration
> ------------------------------------------------------------
>
>                 Key: HDFS-5273
>                 URL: https://issues.apache.org/jira/browse/HDFS-5273
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Haohui Mai
>            Assignee: Haohui Mai
>
> There are multiple switches in the configuration related to HTTPS/SSL, some of which are confusing. For example, _dfs.https.enable_ controls that whether http server will open another port for HTTPS connections, but when _hadoop.ssl.enabled_ is set to true, the original HTTP server only serves HTTPS connections.
> Combining other requirements of setting up secure clusters (e.g., the HTTP port has to be lower than 1024 for a secure datanode), we found that a well-written document is a must-have to overcome the pain of configuring an SSL/HTTPS-enabled cluster.

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