[
https://issues.apache.org/jira/browse/HIVE-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620702#comment-13620702
]
Chris Drome commented on HIVE-4232:
-----------------------------------
In the process of writing some unit tests for the connection string changes I
noticed that the connection type for HiveServer2 defaults to NONE, which uses
the Plain SASL Transport Factory. So in this sense the original implementation
of HiveConnection matches for the default case.
hive.server2.authentication can take one of the following values:
NOSASL
NONE (default)
LDAP
KERBEROS
CUSTOM
I think NONE is misleading and should be renamed PLAIN (or something similar),
and NOSASL should be labelled NONE. And that the default usage of Plain SASL
Transport Factory seems odd. The default behavior of HiveConnection should
match that of HiveServer2.
I'd like to ask your opinion of what the default behavior should be. Should it
default to the Plain SASL transport or no authentication at all?
> JDBC2 HiveConnection has odd defaults
> -------------------------------------
>
> Key: HIVE-4232
> URL: https://issues.apache.org/jira/browse/HIVE-4232
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2, JDBC
> Affects Versions: 0.11.0
> Reporter: Chris Drome
> Assignee: Chris Drome
> Fix For: 0.11.0
>
> Attachments: HIVE-4232.patch
>
>
> HiveConnection defaults to using a plain SASL transport if auth is not set.
> To get a raw transport auth must be set to noSasl; furthermore noSasl is case
> sensitive. Code tries to infer Kerberos or plain authentication based on the
> presence of principal. There is no provision for specifying QOP level.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
