Support Questions

Find answers, ask questions, and share your expertise

Microsoft Kerberos Hive ODBC Error: "No authority could be contacted for authentication"

avatar
Contributor

I encountered below error in my laptop while using the ODBC to Get Data in Power BI Desktop. 

 

My environment:

Hadoop

  • Cloudera quickstart VM 5.13
  • Kerberized with MIT

Laptop

  • Windows 10 64 Bit:
  • Microsoft Hive ODBC 64 bit 2.1
  • MIT Kerberos Ticket Manager installed

 

/etc/krb5.conf
[libdefaults]
default_realm = CLOUDERA
dns_lookup_kdc = false
dns_lookup_realm = false
ticket_lifetime = 86400
renew_lifetime = 604800
forwardable = true
default_tgs_enctypes = rc4-hmac
default_tkt_enctypes = rc4-hmac
permitted_enctypes = rc4-hmac
udp_preference_limit = 1
kdc_timeout = 3000
[realms]
CLOUDERA = {
kdc = quickstart.cloudera
admin_server = quickstart.cloudera
}
[domain_realm]

 

Connect to Kerberized Hive thru Microsoft Hive ODBC:

From Power BI, Get Data -> ODBC -> select my ODBC

I entered username and password in Database tab:

username: cloudera

password: cloudera

 

Error in Power BI while connecting to Hive through the ODBC:

Details: "ODBC: ERROR [HY000] [Microsoft][Hardy] (34) Error from server: SASL(-1): generic failure: Failed to initialize security context: No authority could be contacted for authentication.
.
ERROR [HY000] [Microsoft][Hardy] (34) Error from server: SASL(-1): generic failure: Failed to initialize security context: No authority could be contacted for authentication.

 

I tested the ODBC in 64 Bit ODBC Admin without any errors. In addition, I am able to use the ODBC in DBeaver. 

 

Please shed some light on this error. 

 

Thank you.

10 REPLIES 10

avatar
Contributor

It should be OK because MIT Kerberos client is running fine.

 

[cloudera@~]$ telnet quickstart.cloudera 88
Trying 10.10.10.190...
Connected to quickstart.cloudera.
Escape character is '^]'.
^]

2019-03-16_19-34-54.jpg