You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Brock Noland (JIRA)" <ji...@apache.org> on 2013/12/02 18:42:37 UTC
[jira] [Commented] (HIVE-5812) HiveServer2 SSL connection transport
binds to loopback address by default
[ https://issues.apache.org/jira/browse/HIVE-5812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13836719#comment-13836719 ]
Brock Noland commented on HIVE-5812:
------------------------------------
This looks like a good change, not sure why precommit tests didn't kick off. I tried a second time.
Say, if the delegation token is not null, do we want to call HiveAuthFactory.getSocketTransport(host, port, loginTimeout) to get the transport?
> HiveServer2 SSL connection transport binds to loopback address by default
> -------------------------------------------------------------------------
>
> Key: HIVE-5812
> URL: https://issues.apache.org/jira/browse/HIVE-5812
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Affects Versions: 0.13.0
> Reporter: Prasad Mujumdar
> Assignee: Prasad Mujumdar
> Attachments: HIVE-5812.1.patch
>
>
> The secure socket transport implemented as part of HIVE-5351, binds to loopback address by default. If the bind interface gets used only if its explicitly defined in the hive-site or via environment.
> This behavior should be same as non-SSL transport.
--
This message was sent by Atlassian JIRA
(v6.1#6144)