Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 7 Feb 2015 07:02:35 +0000 (UTC)
From: "Esteban Gutierrez (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12773199.1423292496000.290043.1423292555163@Atlassian.JIRA>
In-Reply-To: <JIRA.12773199.1423292496000@Atlassian.JIRA>
References: <JIRA.12773199.1423292496000@Atlassian.JIRA>
 <JIRA.12773199.1423292496857@arcas>
Subject: [jira] [Created] (HBASE-12984) SSL cannot be used by the InfoPort
 in branch-1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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)