-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KERBEROS auth hive error #128
Comments
Either hive or gohive isn't set up correctly, what is the exception in the hive logs? What is the output of |
after running shell command Ticket cache: FILE:/tmp/krb5cc_1002 Valid starting Expires Service principal then running Ticket cache: FILE:/tmp/krb5cc_1002 Valid starting Expires Service principal |
Probably hive is not configured correctly. What is the stack trace you see in the hive logs when the connection fails? Also you can try to connect with beeline for example and see if it's working, you'd have to do something like |
just work well, kdc just create principal with
not any principal like 'hive/$[email protected]' , Could that be the reason os this? I see this value in a new principal ticket create: but I can't see the hive logs of the current problem right now |
@beltran hive-server2 logs found:
|
Are these or similar parmeters set in hive: https://github.com/beltran/gohive#connect-with-sasl-kerberos? The error I see is what I'd expect if |
I found hive.server2.authentication=KERBEROS in hive-sites.xml,but connected by beeline and I found dual authentication set, https://docs.cloudera.com/documentation/enterprise/latest/topics/cdh_sg_hiveserver2_security.html#topic_9_1_1 sorry, I'm not very familiar with hive and his certification, please |
No problem, then to connect you should do something like this: configuration := gohive.NewConnectConfiguration()
configuration.Username = "hive" // your username
configuration.Service = "password" // your password
=connection, errConn := gohive.Connect("hs2.example.com", 10000, "LDAP", configuration) If you don't have a password you can leave it empty or sett it to |
The problem is still. all service authorization with KERBEROS, So I don't have a LDAP password, with CDH dual authentication set. Why did it create a new one Service principal, host for hive-server2? after |
hmmm, what error are you getting now? Maybe you're using both kerberos and ldap auth, like in the note in this link: https://docs.cloudera.com/documentation/enterprise/latest/topics/cdh_sg_hiveserver2_security.html, in that case you should set |
yes, I set and some others suggestion, why don't we use the same go library |
we connect hive with kerberos, kinit was done, but some wrong happend:
Failed to open Apache Hive connection: Bad SASL negotiation status: 3 (Final handshake step failed)
The text was updated successfully, but these errors were encountered: