My Oracle Support Banner

SASL Connections with Beeline or Impala to HiveServer2 Fails (Doc ID 2031724.1)

Last updated on DECEMBER 04, 2019

Applies to:

Big Data Appliance Integrated Software - Version 4.0 and later
Linux x86-64

Symptoms

NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.

 

SASL connection using beeline client fails with below error ..

beeline> !connect jdbc:hive2://bdanode04.example.com:10000/default;principal=hive/_HOST@BDA.EXAMPLE.COM;saslQop=auth-conf
scan complete in 2ms
Connecting to jdbc:hive2://bdanode04.example.com:10000/default;principal=hive/_HOST@BDA.EXAMPLE.COM;saslQop=auth-conf
Enter username for jdbc:hive2://bdanode04.example.com:10000/default;principal=hive/_HOST@BDA.EXAMPLE.COM;saslQop=auth-conf: <AUTH-CONF1>
Enter password for jdbc:hive2://bdanode04.example.com:10000/default;principal=hive/_HOST@BDA.EXAMPLE.COM;saslQop=auth-conf: <AUTH-CONF2>
15/06/11 16:04:36 [main]: ERROR transport.TSaslTransport: SASL negotiation failure
javax.security.sasl.SaslException: No common protection layer between client and server


Also impala connections using SSL certificates fail

impala-shell --ssl --ca_cert /opt/cloudera/security/jks/impala/node_certificate.pem
Starting Impala Shell without Kerberos authentication
SSL is enabled
Error connecting: TTransportException, Could not connect to bdanode01.example.com:21000
Kerberos ticket found in the credentials cache, retrying the connection with a secure transport.
Error connecting: TTransportException, Could not connect to bdanode01.example.com:21000
Welcome to the Impala shell. Press TAB twice to see a list of available commands.

Copyright (c) 2012 Cloudera, Inc. All rights reserved.

(Shell build version: Impala Shell v1.4.1-cdh5 (201c660) built on Mon Aug 25 18:34:09 PDT 2014)
[Not connected] >

 Beeline or Impala connections work when SASL is not used.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.