We had similar problem using MIT Kerberos Ticket Manager and solution was simple: Uninstall that client, and leave the task to Windows.
How to setup ODBC Connection with Kerberos?
Hello, I'm trying to setup a ODBC connection from Windows Server to Hive data sources. The data sources itself uses a Kerberos for authentication, so it is required kinit or keytab. When i tried to setup the ODBC i always get a error like this:
[Cloudera][DriverSupport] (1170) Unexpected response received from server. Please ensure the server host and port specified for the connection are correct.
I already double check everything, the host and port, yes it is open and i can connect. The realm and domain controller, yes it is all connected. I already install Network Identity Manager and can get a ticket from it. Using kinit is also no problem.
I checked the logs and found something, the username and password is not the same like the one i used in Network Identity Manager and kinit from powershell, something like this
Aug 15 11:11:47.278 INFO 19112 TETSaslClientTransport::SaslLoggingCallback: ::LogUsername: Username returned by QueryCredentialsAttributes(SECPKG_ATTR_NAMES): <windows-username>@<HOSTNAME>
Aug 15 11:11:47.278 ERROR 19112 TETSaslClientTransport::SaslLoggingCallback: ::LogUsername: GetUsernameEx(NameUserPrincipal) failed: 1332
Aug 15 11:11:47.278 DEBUG 19112 TETSaslClientTransport::SaslLoggingCallback: Failed to initialize security context: No credentials are available in the security package
How do i fix it?
SQL Server | Other
2 answers
Sort by: Most helpful
-
-
Bjerre, Henrik 0 Reputation points
2025-08-20T08:05:22.01+00:00 We use Cloudera ODBC Driver for Impala 2.06.17.1026 and Windows Server 2022 Standard.
Mechanism: Kerberos
Canonicalize Principal FQDN UncheckedDeleate Kerberos Credentials Unchecked
Use Keytab Unchecked
Transport Mode SASL