Member since
02-04-2016
132
Posts
52
Kudos Received
7
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
6230 | 07-25-2018 10:53 AM | |
1764 | 07-25-2018 05:15 AM | |
1828 | 10-03-2017 12:08 PM | |
3096 | 04-04-2017 05:36 AM | |
3335 | 11-29-2016 05:40 PM |
02-09-2016
04:20 PM
3 Kudos
Hello Gurus :)
HDP 2.3.2
Ambari 2.1.2.1 I'm trying to setup HiveServer2 with LDAP authentication.
It seems pretty straightforward:
I performed the following:
Changed HiveServer2 Authentication to LDAP
Then i setup my LDAP server url (as the Ambari requested):
Restarted the Hive but hiveserver2.log shows the following during it's startup:
ERROR [HiveServer2-Handler-Pool: Thread-56]: transport.TSaslTransport (TSaslTransport.java:open(315)) - SASL negotiation failure
javax.security.sasl.SaslException: Error validating the login [Caused by javax.security.sasl.AuthenticationException: Error validating LDAP user [Caused by javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1]]] According to the error LDAP 49 - 52e the problem is with the credentials that were passed to the LDAP server.
I don't find any field \ parameter in which i set the LDAP user & password for authentication...
Needless to say that the authentication acts as if it is set to NONE (which is a major problem....) Any ideas ?
Thanks in advance
Adi J.
... View more
Labels:
- Labels:
-
Apache Hive
02-09-2016
09:21 AM
1 Kudo
After changing amb_ranger_admin password in ranger and in Ambari - problem resolved.
What i don't understand is why.
I didn't change this user's password in the first place. I didn't even know this user exists.
I only changed the user called "admin" in Ranger WEB UI & in Ambari.
I never ever touched, edited, updated, changed a user called amb_ranger_admin. Not in Ambari & not in Ranger.
But after setting a new password for this amb_ranger_admin user - in Ambari & in Ranger - problem solved.
Thank you all for your responses. I rewarded points to everyone 🙂
... View more
02-07-2016
05:06 PM
Very similar. The error you posted refers to HDFS.
Mine looks practically the same just with HIVE instead of HDFS.
... View more
02-07-2016
04:59 PM
1 Kudo
Tried every combination including reverting back to the default admin password in Ranger - still no luck.
HiveServer2 won't start as long as it it's Auth are configured using Ranger.
"No JSON object could be decoded" 😞 Thx a million for trying !
... View more
02-07-2016
04:40 PM
Please check if Hive is set for Ranger (Under Security just like in my screenshot).
It might be set to NONE or SQLstdAuth
... View more
02-07-2016
04:08 PM
I updated the 2 locations as described in official docs. Not just one.
... View more
02-07-2016
04:02 PM
1 Kudo
I was referring to HiveServer2 - not Namenode.
In my scenario the Ranger is managing Hive authorization.
So unless Hive isn't set to use Ranger - you won't have this issue.
... View more
02-07-2016
03:40 PM
1 Kudo
I appreciate your offer but no support agreement yet unfortunately. We are still in (advanced) POC stages... Thanks a lot anyways ! Highly appreciated.
... View more
02-07-2016
03:16 PM
1 Kudo
This bug prohibits us from using Ranger which is a great tool for permission governance.
... View more
02-07-2016
03:16 PM
1 Kudo
Hi Neeraj and thank you for your reply ! I've went through this doc and did set the password in both of these places in Ambari >> Ranger.
(Both under "Admin Settings" >>> Ranger Admin user's password for Ambari" & under Advanced ranger-env >>> admin password).However - problem remains. It is very easy to reproduce - just change Ranger's admin password in UI + both places in Ambari and see for yourself. HiveServer2, if configured to authorize using Ranger, won't start.
It has been confirmed and consistent on two different clusters.
... View more
- « Previous
- Next »