Support Questions

Find answers, ask questions, and share your expertise

Impala ODBC settings with Kerberos

Explorer

Hello,

 

We have a kerberized clúster and a user of us tells that the next setting on the ODBC for Impala is not working

 

impala <- src_impala(
  drv = drv,
  driver = "/opt/cloudera/impalaodbc/lib/64/libclouderaimpalaodbc64.so",
  host = "hostname",
  port = 21050,
  database = "publication",
  KrbRealm = "CLOUDERA",
  KrbFQDN = "hostname",
  KrbServiceName = "impala",
  AuthMech = 1,
  UseKeytab = 1,
  UPNKeytabMappingFile = "/home/gentrif/talend.keytab"
)

 

Looking into the documentation I told them to use the next setting

 

impala <- src_impala(
  drv = drv,
  driver = "/opt/cloudera/impalaodbc/lib/64/libclouderaimpalaodbc64.so",
  host = "hostname",
  port = 21050,
  database = "publication",
  KrbRealm = "CLOUDERA",
  KrbFQDN = "hostname",
  KrbServiceName = "impala",
  AuthMech = 1,
  UseKeytab = 1,
  DefaultKeytabFile = "/home/gentrif/talend.keytab"
  uid = "principal"
)

 

As the user tells us this last configuration is not working for their application.

 

Maybe we are forgeting something important.

 

Thank you in advance

1 ACCEPTED SOLUTION

Explorer

Hello everybody,

 

The settings we provided the app developers in the client side was right, they had some problem with /etc/hosts configuration making them to not authenticating properly to the KDC server, also, they had a bad /etc/krb5.conf.

 

With that I close this topic

View solution in original post

3 REPLIES 3

Explorer

Hello everybody,

 

The settings we provided the app developers in the client side was right, they had some problem with /etc/hosts configuration making them to not authenticating properly to the KDC server, also, they had a bad /etc/krb5.conf.

 

With that I close this topic

Explorer

Where did you get the .keytab file?  Was it generated on the client side or server side? How was it generated?

 

here's the error msg iget from command isql -v <serveraddress>

 

[08S01][unixODBC][Cloudera][ImpalaODBC] (100) Error from the Impala Thrift API: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Server not found in Kerberos database)

Explorer

keytab file was generated on server side.

 

Anyway the issue is solved, the machine where the ODBC client was being developed had /etc/krb5.conf and /etc/hosts both wrong.

 

Anyway thank you for your reply 🙂

Take a Tour of the Community
Don't have an account?
Your experience may be limited. Sign in to explore more.