[HIVE-12688] HIVE-11826 makes hive unusable in properly secured cluster

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.3.0, 2.0.0
• Fix Version/s: 2.0.0
• Target Version/s: 1.3.0, 2.0.0
• Assignee: Thejas Nair
• Reporter: Thejas Nair
• Created: 16/Dec/15 05:34
• Updated: 02/Jun/16 10:17
• Resolved: 18/Dec/15 00:00

Description

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.

Issue Links

• is broken by: HIVE-11826 'hadoop.proxyuser.hive.groups' configuration doesn't prevent unauthorized user to access metastore