Summary
After changing ‘Authentication Backend Order’ to external, users cannot login. This guide explains how to revert back to default behaviour, authenticating through database first.
Symptoms
Users cannot login to Cloudera Manager
Conditions
Cloudera Manager boots up
Login page accessible through the browser
External authentication is enabled (LDAP, LDAP with TLS = LDAPS)
Authentication Backend Order, was changed to external authentication.
Cause
Cloudera Manager is trying to connect to LDAP If auth_backend_order is set to external only or external and DB. A misconfiguration with LDAP or External authentication is causing Cloudera Manager Server to unable to map users credential appropriately.
Instructions
Please follow the instructions to fix this.
Note: Take backup of the SCM database [0]
By deleting auth_backend_order order config Cloudera Manager falls back to the DB_ONLY auth backend and will not try to connect to the LDAP server.
Step 1:
Stop the Cloudera Manager server
$sudo service cloudera-scm-server stop
Confirm the auth_backend_order is other than non-default ie: not DB_ONLY or nothing.
Step – 2:
Run this query in the Cloudera Manager schema to reset the Authentication Backend Order configuration:
Connect mysql DB:
./mysql -u root -p
mysql>use scm;
mysql> select ATTR, VALUE from CONFIGS where ATTR = “auth_backend_order”;
Delete the auth_backend_order attribute from Cloudera Manager database (this will revert to default behavior). Run below query in the Cloudera Manager schema to reset the Authentication Backend Order configuration:
mysql> delete from CONFIGS where ATTR = “auth_backend_order” and SERVICE_ID is null;
Step – 3:
Start the Cloudera Manager server
$sudo service cloudera-scm-server start
Try to login now with admin user.
