You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Esteban Gutierrez (JIRA)" <ji...@apache.org> on 2015/02/07 08:02:35 UTC

[jira] [Created] (HBASE-12984) SSL cannot be used by the InfoPort in branch-1

Esteban Gutierrez created HBASE-12984:
-----------------------------------------

             Summary: 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
            Priority: Blocker


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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)