You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Thejas M Nair (JIRA)" <ji...@apache.org> on 2014/03/11 11:19:44 UTC

[jira] [Comment Edited] (HIVE-6486) Support secure Subject.doAs() in HiveServer2 JDBC client.

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

Thejas M Nair edited comment on HIVE-6486 at 3/11/14 10:18 AM:
---------------------------------------------------------------

There is no server side impact of this feature. The server side should be configured for 'secure(/kerberos)' mode.
The server side doc does not require changes.




was (Author: thejas):
There is no server side impact of this feature. The server side should be configured for 'secure(/kerberos)' mode.


> Support secure Subject.doAs() in HiveServer2 JDBC client.
> ---------------------------------------------------------
>
>                 Key: HIVE-6486
>                 URL: https://issues.apache.org/jira/browse/HIVE-6486
>             Project: Hive
>          Issue Type: Improvement
>          Components: Authentication, HiveServer2, JDBC
>    Affects Versions: 0.11.0, 0.12.0
>            Reporter: Shivaraju Gowda
>            Assignee: Shivaraju Gowda
>             Fix For: 0.13.0
>
>         Attachments: HIVE-6486.1.patch, HIVE-6486.2.patch, HIVE-6486.3.patch, Hive_011_Support-Subject_doAS.patch, TestHive_SujectDoAs.java
>
>
> HIVE-5155 addresses the problem of kerberos authentication in multi-user middleware server using proxy user.  In this mode the principal used by the middle ware server has privileges to impersonate selected users in Hive/Hadoop. 
> This enhancement is to support Subject.doAs() authentication in  Hive JDBC layer so that the end users Kerberos Subject is passed through in the middle ware server. With this improvement there won't be any additional setup in the server to grant proxy privileges to some users and there won't be need to specify a proxy user in the JDBC client. This version should also be more secure since it won't require principals with the privileges to impersonate other users in Hive/Hadoop setup.
>  



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