[
https://issues.apache.org/jira/browse/HBASE-12984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Esteban Gutierrez updated HBASE-12984:
--------------------------------------
Assignee: Esteban Gutierrez
Status: Patch Available (was: Open)
> SSL cannot be used by the InfoPort in branch-1
> ----------------------------------------------
>
> Key: HBASE-12984
> URL: https://issues.apache.org/jira/browse/HBASE-12984
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.0.0, 2.0.0, 1.1.0
> Reporter: Esteban Gutierrez
> Assignee: Esteban Gutierrez
> Priority: Blocker
> Attachments: HBASE-12984-v1.txt
>
>
> Setting {{hbase.ssl.enabled}} to {{true}} doesn't enable SSL on the
> InfoServer. Found that the problem is down the InfoServer and HttpConfig in
> how we setup the protocol in the HttpServer:
> {code}
> for (URI ep : endpoints) {
> Connector listener = null;
> String scheme = ep.getScheme();
> if ("http".equals(scheme)) {
> listener = HttpServer.createDefaultChannelConnector();
> } else if ("https".equals(scheme)) {
> SslSocketConnector c = new SslSocketConnectorSecure();
> c.setNeedClientAuth(needsClientAuth);
> c.setKeyPassword(keyPassword);
> {code}
> It depends what end points have been added by the InfoServer:
> {code}
> builder
> .setName(name)
> .addEndpoint(URI.create("http://"; + bindAddress + ":" + port))
> .setAppDir(HBASE_APP_DIR).setFindPort(findPort).setConf(c);
> {code}
> Basically we always use http and we don't look via HttConfig if
> {{hbase.ssl.enabled}} was set to true and we assign the right schema based on
> the configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
