Created on 12-08-2014 11:28 AM - edited 09-16-2022 02:14 AM
Hi,
I am trying to enable LDAP in impala but it gives me an error like this :-
12:04:40.393 PM INFO thrift-util.cc:105
TThreadPoolServer: TServerTransport died on accept: SASL(-13): user not found: Password verification failed
12:05:11.899 PM INFO thrift-util.cc:105
TThreadPoolServer: TServerTransport died on accept: invalid sasl status
12:13:09.242 PM INFO thrift-util.cc:105
TThreadPoolServer: TServerTransport died on accept: invalid sasl status
12:13:44.246 PM INFO authentication.cc:235
Trying simple LDAP bind for:xxxx
12:13:44.250 PM WARN authentication.cc:242
LDAP authentication failure for xxxx : Invalid credentials
12:13:44.250 PM ERROR authentication.cc:148
SASL message (LDAP): Password verification failed
12:13:44.251 PM INFO thrift-util.cc:105
TThreadPoolServer: TServerTransport died on accept: SASL(-13): user not found: Password verification failed
12:13:58.467 PM INFO authentication.cc:235
Trying simple LDAP bind for: xxxx
12:13:58.471 PM WARN authentication.cc:242
LDAP authentication failure for xxxx : Invalid credentials
12:13:58.471 PM ERROR authentication.cc:148
SASL message (LDAP): Password verification failed
12:13:58.472 PM INFO thrift-util.cc:105
TThreadPoolServer: TServerTransport died on accept: SASL(-13): user not found: Password verification failed
Even though i am giving the correct credentials.
I have enabled LDAP in IMpala by giving LDAP_url,Enable LDAP authentication,TLS checkbox(without this enabled Impala does not start) and added these properties in advanced command line impala code snippet in cloudera manager :-
-ldap_domain=
-base_dn=
-bind_dn=
-bind_password=
Also,when i login through hue (LDAP enabled) ,i get impala error on the landing page even though the impala daemon is up and running and giving no error in log file:-
Potential misconfiguration detected. Fix and restart Hue.
Impala Editor No available Impalad to send queries to.
I am using CDH 5.2 on RED hat linux 6.5
Created 12-12-2014 08:19 AM
This issue got resolved by adding --ldap_domain in advanced Snippet Command line argument for impala daemon.
After restarting the service,
doing impala-shell -l in linux terminal
prompted for ldap username's password and got successfuly connected.
Created 12-12-2014 08:19 AM
This issue got resolved by adding --ldap_domain in advanced Snippet Command line argument for impala daemon.
After restarting the service,
doing impala-shell -l in linux terminal
prompted for ldap username's password and got successfuly connected.