hive-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mich Talebzadeh <mich.talebza...@cloudtechnologypartners.co.uk>
Subject Hive release 2.0 beeline authentication issue
Date Mon, 22 Feb 2016 16:56:42 GMT
 

Hi, 

Just upgraded from Hive 1.2.1 to Hive 2. Hive connection works OK and
Hive server started OK as well. 

When I use beeline command below it used to work in Hive 1.2.1 However,
now I get this error message: 

BEELINE -U JDBC:HIVE2://RHES564:10010/DEFAULT
ORG.APACHE.HIVE.JDBC.HIVEDRIVER -N HDUSER -P XXXX 

Error: Failed to open new session: java.lang.RuntimeException:
org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.authorize.AuthorizationException):
User: hduser is not allowed to impersonate hduser (state=,code=0)
Beeline version 2.0.0 by Apache Hive 

I have these in hive-site.xml 

 <property>
 <name>hive.metastore.sasl.enabled</name>
 <value>false</value>
 <description>If true, the metastore Thrift interface will be secured
with SASL. Clients must authenticate with Kerberos.</description>
 </property> 

 <property>
 <name>hive.server2.authentication</name>
 <value>NONE</value>
 <description>
 Expects one of [nosasl, none, ldap, kerberos, pam, custom].
 Client authentication types.
 NONE: no authentication check
 LDAP: LDAP/AD based authentication
 KERBEROS: Kerberos/GSSAPI authentication
 CUSTOM: Custom authentication provider
 (Use with property hive.server2.custom.authentication.class)
 PAM: Pluggable authentication module
 NOSASL: Raw transport
 </description>
 </property> 

Any ideas what has changed? 

Thanks 

-- 

Dr Mich Talebzadeh

LinkedIn
https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw

http://talebzadehmich.wordpress.com

NOTE: The information in this email is proprietary and confidential.
This message is for the designated recipient only, if you are not the
intended recipient, you should destroy it immediately. Any information
in this message shall not be understood as given or endorsed by Cloud
Technology Partners Ltd, its subsidiaries or their employees, unless
expressly so stated. It is the responsibility of the recipient to ensure
that this email is virus free, therefore neither Cloud Technology
partners Ltd, its subsidiaries nor their employees accept any
responsibility.

 
Mime
View raw message