You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Misty Stanley-Jones (JIRA)" <ji...@apache.org> on 2015/08/10 01:47:46 UTC

[jira] [Assigned] (HBASE-12983) HBase book mentions hadoop.ssl.enabled when it should be hbase.ssl.enabled

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

Misty Stanley-Jones reassigned HBASE-12983:
-------------------------------------------

    Assignee: Misty Stanley-Jones

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