[28000][unixODBC][Cloudera][ThriftExtension] (9) Error occurred while authenticating via SASL. Error details: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No Kerberos credentials available (default cache: KEYRING:persistent:0)) [ISQL]ERR

[#1]

Hello.

I am trying to connect to an Cloudera server, from another server (its an php web server).
Everything has been setup correctly on the php server side. However, i'm still getting the error mentioned in the subject when trying to connect:

[28000][unixODBC][Cloudera][ThriftExtension] (9) Error occurred while authenticating via SASL. Error details: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No Kerberos credentials available (default cache: KEYRING:persistent:0))
[ISQL]ERROR: Could not SQLConnect

My authentication is local, so i've set AuthMech to 1.
No SSL for connecting into the server (not needed)
I can connect from the php server to the cloudera host (tested with an telnet)
The credentials are okay (since i can connect using the web browser).

The php server is an RHEL Version 7.6

And the log isn't working. I manually created the file, changed its permissions, but nothing is being logged.

I'll put my configurations here. Any input is very appreciated.
Thanks a lot for your attention.

odbc.ini

[HiveDSN]
Driver=Cloudera ODBC Driver for Apache Hive
Description=Cloudera Hive ODBC
Host=cloudera17.org.com.net
Port=10000
Database=database_hidden
AuthMech=1
UID=THEUSER
PWD=SDSDSDSDSDSD
Trace=Yes
TraceFile=/var/log/odbc_out.log
UseSASL=0
KerberosAuth=0

odbcinst.ini

[Cloudera ODBC Driver for Apache Hive]
Description=Cloudera ODBC Driver for Apache Hive
Driver=/opt/cloudera/hiveodbc/lib/64/libclouderahiveodbc64.so
UsageCount=3

[#2]

@pablobhz Welcome to the Cloudera Community!

To help you get the best possible solution, I have tagged our Hive experts @mszurap @cravani  who may be able to assist you further.

Please keep us updated on your post, and we hope you find a satisfactory solution to your query.

[#3]

Thanks Diana! I'll be looking forward to it.
On my Cloudera Cluster, i have as sources both Impala and Hive. I've also tried to connect to Impala (another DSN) but it didn't worked out =(

And the hive connection displays the error i mentioned. I spent the day working on it but couldn't figure out what is happening.

[#4]

Hello @pablobhz ,

Please look at the ODBC driver documentation, installation guide (this is for version 2.8.0):

https://www.cloudera.com/downloads/connectors/hive/odbc/2-8-0.html

Which driver version are you using? And what is the cluster version?

The "AuthMech=1" corresponds to the Kerberos based authentication mode, that's why the connector tried to connect with Kerberos.

The "AuthMech=0" means no authentication is needed.

Is the cluster Kerberos enabled? If yes, then it is not possible to connect without some credentials.

If the cluster (Hive service) is indeed kerberos enabled, then the "No Kerberos credentials available" and the "default cache: KEYRING:persistent:0" shows that the krb5.conf / "default_ccache_name " has been configured to use keyring. Instead of that please use a ticket cache file with the "FILE" based, see

https://web.mit.edu/kerberos/krb5-1.12/doc/basic/ccache_def.html 

As I see there is no "KerberosAuth" configuration option for the latest ODBC driver. 

Thanks

 Miklos

[#5]

@pablobhz Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.  Thanks.