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

Posted to dev@hive.apache.org by "Vaibhav Gumashta (JIRA)" <ji...@apache.org> on 2014/08/18 12:05:18 UTC

[jira] [Updated] (HIVE-7764) Support all JDBC-HiveServer2 authentication modes on a secure cluster

     [ https://issues.apache.org/jira/browse/HIVE-7764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vaibhav Gumashta updated HIVE-7764:
-----------------------------------

    Attachment: HIVE-7764.1.patch

> Support all JDBC-HiveServer2 authentication modes on a secure cluster
> ---------------------------------------------------------------------
>
>                 Key: HIVE-7764
>                 URL: https://issues.apache.org/jira/browse/HIVE-7764
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2, JDBC
>    Affects Versions: 0.14.0
>            Reporter: Vaibhav Gumashta
>            Assignee: Vaibhav Gumashta
>             Fix For: 0.14.0
>
>         Attachments: HIVE-7764.1.patch
>
>
> Currently, HiveServer2 logs in with its keytab only if hive.server2.authentication is set to KERBEROS. However, hive.server2.authentication is config that determines the auth type an end user will use while authenticating with HiveServer2. There is a valid use case of user authenticating with HiveServer2 using LDAP for example, while HiveServer2 runs the query on a kerberized cluster.



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