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

Aihua Xu commented on HIVE-12688:
---------------------------------

You are right. This is hadoop property. Seems that property should not limit 
the access to metastore server and we were historically using that to limit 
access to hive.

In our own version, somehow we documented as such. Is this the old behavior? 
Instead of changing it back since it will introduce the issue that it will not 
block unauthorized access to Hive, can we keep this behavior and try to rework 
with a correct way that we block the Hive access somewhere else in a later 
version? 


> HIVE-11826 makes hive unusable in properly secured cluster
> ----------------------------------------------------------
>
>                 Key: HIVE-12688
>                 URL: https://issues.apache.org/jira/browse/HIVE-12688
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 1.3.0, 2.0.0
>            Reporter: Thejas M Nair
>            Assignee: Thejas M Nair
>            Priority: Blocker
>         Attachments: HIVE-12688.1.patch
>
>
> HIVE-11826 makes a change to restrict connections to metastore to users who 
> belong to groups under 'hadoop.proxyuser.hive.groups'.
> That property was only a meant to be a hadoop property, which controls what 
> users the hive user can impersonate. What this change is doing is to enable 
> use of that to also restrict who can connect to metastore server. This is new 
> functionality, not a bug fix. There is value to this functionality.
> However, this change makes hive unusable in a properly secured cluster. If 
> 'hadoop.proxyuser.hive.hosts' is set to the proper set of hosts that run 
> Metastore and Hiveserver2 (instead of a very open "*"), then users will be 
> able to connect to metastore only from those hosts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to