Use the chuser command to change the
attributes of an existing user.
Syntax
chuser [ { -password [cleartext_password] | -nopassword } ] [ { -keyfilesshkey_filename | -nokey } ] [ -remote { yes | no } ] [ -usergrp { group_name | group_id } ] { user_name | user_id }
Parameters
- -password cleartext_password
- (Optional) Specifies the new password to be associated with the
user. The password cannot start or end with a blank. It must consist
of a string of 6 - 64 printable ASCII characters. You can optionally
specify the password with the password parameter.
If you do not specify the password, the system prompts you for it
before running the command and does not display the password that
you type. Either the password parameter or the nopassword parameter
can be set.
- -nopassword
- (Optional) Specifies that the user's password is to be deleted.
- -keyfile sshkey_filename
- (Optional) Specifies the name of the file that contains the Secure
Shell (SSH) public key. Either the keyfile parameter
or the nokey parameter can be set.
- -nokey
- (Optional) Specifies that the user's SSH key is to be deleted.
- -remote yes | no
- (Optional) Specifies whether the user authenticates to the cluster
using a remote authentication service. Either yes or no must
be set.
- -usergrpgroup_name | group_id
- (Optional) Specifies the new group for the user.
- user_name | user_id
- (Required) Specifies the user whose attributes are to be changed.
Description
Use
the chuser command to modify the attributes of
an existing user.
You must have the Security Administrator role
to create, delete, or change a user.
Only use the usergrp parameter
for local users. If you change a user from local to remote, the user's
association with any group is removed.
If you change a user
from remote to local, a user group must be specified. If you change
a user from local to remote, the user must have both a password and
an SSH key.
If you use the keyfile parameter,
the SSH key file should be placed in the /tmp directory
before running this command. When you run the command, the SSH key
is copied into cluster state and activated for the user, and the input
file is deleted.
An invocation example
chuser -remote no -usergrp Monitor -nokey jane
The
resulting output:
No feedback