[
https://issues.apache.org/jira/browse/HBASE-12983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946276#comment-14946276
]
Hudson commented on HBASE-12983:
--------------------------------
FAILURE: Integrated in HBase-TRUNK #6880 (See
[https://builds.apache.org/job/HBase-TRUNK/6880/])
HBASE-12983 HBase book mentions hadoop.ssl.enabled when it should be
(mstanleyjones: rev bd9a41a3685ec3f42776b89b756e121c02640b93)
* src/main/asciidoc/_chapters/security.adoc
> HBase book mentions hadoop.ssl.enabled when it should be hbase.ssl.enabled
> --------------------------------------------------------------------------
>
> Key: HBASE-12983
> URL: https://issues.apache.org/jira/browse/HBASE-12983
> Project: HBase
> Issue Type: Bug
> Components: documentation
> Reporter: Esteban Gutierrez
> Assignee: Misty Stanley-Jones
> Fix For: 2.0.0
>
> Attachments: HBASE-12983.patch
>
>
> In the HBase book we say the following:
> {quote}
> A default HBase install uses insecure HTTP connections for web UIs for the
> master and region servers. To enable secure HTTP (HTTPS) connections instead,
> set *hadoop.ssl.enabled* to true in hbase-site.xml. This does not change the
> port used by the Web UI. To change the port for the web UI for a given HBase
> component, configure that port’s setting in hbase-site.xml. These settings
> are:
> {quote}
> The property should be *hbase.ssl.enabled* instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
