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

Chris Drome commented on HIVE-4232:
-----------------------------------

The patch proposes that if auth is not specified or auth=none the transport 
will default to TSocket. If auth=kerberos|plain then the Kerberos SASL 
transport or the Plain SASL transport will be used. If auth=kerberos then 
principal must also be specified. We propose controlling the QOP with another 
parameter qop=auth|auth-int|auth-conf. The patch also takes care of 
case-sensitive value comparisons.

I feel that these changes result in a more reasonable set of defaults and don't 
rely upon inferring Kerberos or plain based on the existence of other 
parameters.

I will rebase HIVE-4225 if these proposed changes are accepted.
                
> 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
>         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

Reply via email to