Reply
Master
Posts: 429
Registered: ‎07-01-2015
Accepted Solution

Cannot connect to Impala via ODBC

[ Edited ]

Hi,

 does anybody know what exactly this error means?

[Cloudera][ImpalaODBC] (100) Error from the Impala Thrift API: SASL(-1): generic failure: Failed to initialize security context: No credentials are available in the security package

 

I have a ODBC driver 2.5.41 connecting to Impala daemon, the user has a valid ticket in the Windows machine, but the driver refuse to connect. Mechanism is Kerberos, service name, keytab .. all configured in ODBC Setup.

 

The impala daemon does not show any particular meaningful message in the logs about the login attempt,

 

Thanks

Expert Contributor
Posts: 136
Registered: ‎07-17-2017

Re: Cannot connect to Impala via ODBC

Hi @Tomas79

Check the value of your params

SSL=
UseSASL=

in odbc.ini

Highlighted
Explorer
Posts: 11
Registered: ‎01-31-2019

Re: Cannot connect to Impala via ODBC

Hi

 

What are the values to be passed for these parameters

 

 

SSL= 1
UseSASL=0

 

Description=
Driver=
HOST=

PORT=
Database=dbname
AuthMech=4
UID=username
PWD=password
SSL=1
CAIssuedCertNamesMismatch=1
TrustedCerts=
KrbFQDN=
KrbRealm=
KrbServiceName=
TSaslTransportBufSize=1000
RowsFetchedPerBlock=10000
SocketTimeout=0
StringColumnLength=32767
UseNativeQuery=0

Explorer
Posts: 11
Registered: ‎01-31-2019

Re: Cannot connect to Impala via ODBC

<used SASL>

Explorer
Posts: 11
Registered: ‎01-31-2019

Re: Cannot connect to Impala via ODBC


@Hadoopuser wrote:

Hi

 

What are the values to be passed for these parameters

 

 

SSL= 1
UseSASL=0

 

Description=
Driver=
HOST=

PORT=
Database=dbname
AuthMech=4
UID=username
PWD=password
SSL=1
CAIssuedCertNamesMismatch=1
TrustedCerts=
KrbFQDN=
KrbRealm=
KrbServiceName=
TSaslTransportBufSize=1000
RowsFetchedPerBlock=10000
SocketTimeout=0
StringColumnLength=32767
UseNativeQuery=0



<used SASL>

Explorer
Posts: 11
Registered: ‎01-31-2019

Re: Cannot connect to Impala via ODBC

Yes