You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "omicron (JIRA)" <ji...@apache.org> on 2014/03/03 08:19:22 UTC

[jira] [Commented] (HIVE-6517) Improvement on HiveSever2 JDBC: in Kerberos auth mode, accept username / password passed from the client's SessionConf

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

omicron commented on HIVE-6517:
-------------------------------

i agree， and now hive can not handle the query command from cli or beeline if there is no kerberos ticket cache in the local

> Improvement on HiveSever2 JDBC: in Kerberos auth mode, accept username / password passed from the client's SessionConf
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-6517
>                 URL: https://issues.apache.org/jira/browse/HIVE-6517
>             Project: Hive
>          Issue Type: Improvement
>          Components: Authentication, HiveServer2, JDBC
>            Reporter: Jacob Magner
>            Assignee: Prasad Mujumdar
>
> The default JDBC driver ignores username/password completely in Kerberos auth mode.
> To be able to auth from a web interface, we could enable password pass through by changing
> how the Kerberos transport is established. Specifically, we could use LoginContext to authenticate
> with the kdc, and then use the resulting security context to connect with the hive server.



--
This message was sent by Atlassian JIRA
(v6.2#6252)