[
https://issues.apache.org/jira/browse/HDFS-5538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao updated HDFS-5538:
----------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
I've committed this to trunk. We can merge it to branch-2 after the remaining
work done and well tested.
> 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
> Fix For: 3.0.0
>
> 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 up.
> 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 https.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
