hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12984) SSL cannot be used by the InfoPort after removing deprecated code in HBASE-10336
Date Sun, 08 Feb 2015 07:32:35 GMT

    [ https://issues.apache.org/jira/browse/HBASE-12984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14311153#comment-14311153
] 

stack commented on HBASE-12984:
-------------------------------

I tried to test it myself but having some trouble getting past:

Caused by: java.io.IOException: !JsseListener: java.lang.NullPointerException

It causes us to fail startup.  Looks like HDFS-3059 and its complaint that ssl-server.xml
is required but we don't seem to load ssl-server.xml anywhere.

Was following these instructions: http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.1.3/bk_reference/content/ch_wire-https.html
Looks like we have a bit of a hole in our refguide hereabouts.

Maybe you have more luck [~esteban]?

> SSL cannot be used by the InfoPort after removing deprecated code in HBASE-10336
> --------------------------------------------------------------------------------
>
>                 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
>             Fix For: 1.0.0, 2.0.0, 1.1.0
>
>         Attachments: HBASE-12984-v1.txt, HBASE-12984-v3.txt, HBASE-12984-v3.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)

Mime
View raw message