This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
on 03-22-201602:38 PM - edited on 08-06-201909:35 AM by SonaliM
When trying to connect to Impala or Hive using a Kerberized instance, an error appears: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Internal Credentials Cache error).
Windows Operation System
A Hadoop instance with Impala or Hive and the appropriate ODBC driver
Confirm that you are using Kerberos SSPI by asking your DB Admin and/or IT.
If you manually generate a Kerberos ticket through the MIT Kerberos client or a kinit command, you are not using Kerberos SSPI.
The "Internal Credentials Cache error" means that Alteryx cannot find the Kerberos ticket needed for authentication to connect to the Hadoop instance. By default, the ODBC driver uses the GSSAPI library to handle Kerberos authentication. With the GSSAPI library, Alteryx is trying to located a Kerberos ticket in the credentials cache but is unable to do so because Kerberos SSPI does not use the credentials cache.
Make sure you have the latest Simba Impala or Hive driver for the next steps.
1. Open the Windows ODBC Administrator
2. Select the User or System Impala DSN that you have configured and press Configure:
3. Once in the Simba Impala ODBC Driver DSN Setup window, press on Advanced Options:
4. Under Advanced Options, check the Enable for this DSN for the Use Only SSPI:
5. Press OK.
6. Click "Test" in the main ODBC DSN Window to make sure the connection works.
7. Start Alteryx and test your connection in an Input tool.