hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haohui Mai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5538) URLConnectionFactory should pick up the SSL related configuration by default
Date Mon, 25 Nov 2013 22:58:37 GMT

    [ https://issues.apache.org/jira/browse/HDFS-5538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832027#comment-13832027

Haohui Mai commented on HDFS-5538:

We'll defer the system test of HA / QJM in HDFS-5545 / HDFS-5536.

> URLConnectionFactory should pick up the SSL related configuration by default
> ----------------------------------------------------------------------------
>                 Key: HDFS-5538
>                 URL: https://issues.apache.org/jira/browse/HDFS-5538
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Haohui Mai
>            Assignee: Haohui Mai
>         Attachments: HDFS-5538.000.patch, HDFS-5538.001.patch, HDFS-5538.002.patch, HDFS-5538.003.patch
> The default instance of URLConnectionFactory, DEFAULT_CONNECTION_FACTORY does not pick
up any hadoop-specific, SSL-related configuration. Its customers have to set up the ConnectionConfigurator
explicitly in order to pick up these configurations. This is less than ideal for HTTPS because
whenever the code needs to make a HTTPS connection, the code is forced to go through the set
> This jira refactors URLConnectionFactory to ease the handling of HTTPS connections (compared
to the DEFAULT_CONNECTION_FACTORY we have right now). In particular, instead of loading the
SSL configurator statically in SecurityUtil (based on a global configuration about SSL), and
determine whether we should set up SSL for a given connection based on whether the SSL configurator
is null, we now load the SSL configurator in URLConnectionFactory, and determine if we need
to use the configurator to set up an SSL connection based on if the given URL/connection is

This message was sent by Atlassian JIRA

View raw message