@Selene Please take a backup of database and then you can follow below steps: Find the Cloudera Manager server's database details from file /etc/cloudera-scm-server/db.properties . Log in to CM database server. Check if there is more than one user admin in the system. Take a back up of password_hash and password_salt of the Admin user and paste them into a text editor: SELECT password_hash, password_salt FROM users WHERE user_id = 1; Update password_hash and password_salt for user "admin" using the following command: update USERS set password_hash='2518db3278f704558ece63f469af87a7c12dbad8ff0971d3b677e291d61b44fc', password_salt=-5792243850706636683 WHERE user_id = 1; Log in to the CM interface using admin user and admin password .
... View more
@Selene Have each account for each service is more secure because each account have it's own unix groups and privileges. Think of this way if one account got issue, complete ecosystem will in problem and secondly account id's like hdfs, yarn have there own privileges of permissions to execute few commands which can't be shared. Think of today's modernized applications how each of them are running as macro services. Technically speaking we can do it but you need to rewrite alot of code if you prefer to do. My suggestion go with service account.
... View more