Changing the Password for a Component Running User

Scenario

The administrator is advised to periodically change the password for each component running user to improve the system O&M security.

Component running users can be classified into the following two types depending on whether their initial passwords are randomly generated by the system:

If the initial password of a component running user is randomly generated by the system, the user is of the machine-machine type.
If the initial password of a component running user is not randomly generated by the system, the user is of the human-machine type.

Impact on the System

If the initial password is randomly generated by the system, the cluster needs to be restarted for the password changing to take effect. Services are unavailable during the restart.

Prerequisites

You have installed the client on any node in the cluster and obtained the IP address of the node.

Procedure

Log in to the node where the client is installed as the client installation user
Run the following command to switch to the client directory, for example, /opt/client:

cd /opt/client
Run the following command to set environment variables:

source bigdata_env
Run the following command and enter the password of user kadmin/admin to log in to the kadmin console:

kadmin -p kadmin/admin

The default password of user kadmin/admin is Admin@123. The password will expire upon your first login. Change the password as prompted. Keep the password secure because it cannot be retrieved once lost.
Run the following command to change the password of an internal component running user.

cpw Internal system username

Example: cpw hdfs

User hdfs is an example. Replace it with the actual username.

The password must meet the following complexity requirements:
- Contains at least 8 characters.
- Contains at least four types of the following: uppercase letters, lowercase letters, numbers, spaces, and special characters (~`!?,.;-_'(){}[]/<>@#$%^&*+|\=).
- Cannot be the same as the username or the username spelled backwards.
- Cannot be a common easily-cracked password, for example, Admin@12345.
- Cannot be the same as the password used in latest N times. N indicates the value of Number of Historical Passwords configured in Configuring Password Policies. This policy applies to only human-machine accounts.
Run the following command to check user information:

getprinc Internal system username

Example: getprinc hdfs
Determine the type of the user whose password needs to be changed.
- If the user is a machine-machine user, go to 7.
- If the user is a human-machine user, the password is changed successfully and no further action is required.
Log in to FusionInsight Manager.
On the home page, click or More and click Restart.
In the displayed window, enter the password of the current login user and click OK.
In the displayed restart confirmation dialog box, click OK.
Wait for message "Operation successful" to display.