account
This command allows you to create and manage users and groups.
Any changes you make to users and groups will be applied immediately, although users who are currently logged in will not see the effect of your changes until the log out and log back in again.
The account
command is for managing local user accounts. As an alternative to managing a set of local user accounts in SuperADMIN, you can connect SuperSTAR to an external authentication service such as Active Directory or LDAP. See
these instructions to learn more
.
Usage | Description | ||||||
---|---|---|---|---|---|---|---|
account <id> | Displays information about the specified user account or group. | ||||||
account users | Displays a list of all the configured user accounts. | ||||||
account groups | Displays a list of all the configured groups. | ||||||
account creategroup <group_id> [ <display_name> ] |
Creates a new group.
| ||||||
account createuser <user_id> [ <display_name> ] [ <password> ] |
Creates a new user.
When you create a new user, that user will not have access to any datasets by default. You must either add the user to a group that has access to the appropriate datasets, or use the | ||||||
account <group_id> users | Displays a list of users who are members of the specified group. | ||||||
account <user_id> memberships | Displays a list of groups that the specified user belongs to. | ||||||
account <user_id> addmembership <group_id> | Adds the specified user to the specified group. | ||||||
account <group_id> adduser <user_id> | Adds the specified user to the specified group. | ||||||
account <group_id> removeuser <user_id> | Removes the specified user from the specified group. | ||||||
account <id> remove | Deletes the specified user or group. | ||||||
account <id> displayname <new_display_name> | Changes the display name for the specified user or group. | ||||||
account maxattempts <value> | Sets the default number of failed login attempts before an account will be locked. This will be the default setting and will apply to all users unless a different setting has been specifically applied to an individual user account. | ||||||
account <id> maxattempts <value> | Sets the maximum number of failed login attempts before an account will be locked. This is the same as the previous command, except that it applies to a specific user account only. | ||||||
account locktime <seconds> |
Sets the number of seconds to lock an account once the user has exceeded the maximum failed login attempts. During this time the user will not be able to login even if they specify the correct credentials. For example, if If you set | ||||||
account <id> locktime <seconds> | Sets the number of seconds to lock an account. This is the same as the previous command, except that it applies to a specific user account only. | ||||||
account <id> {lock|unlock} | Locks or unlocks the specified user account. | ||||||
account updateloginentry {true|false} |
Enables or disables the logging of a user's last successful login time. You are recommended to set this to | ||||||
account <user_id> setpassword |
Changes the password of the specified user. Use this command to reset a user's password (for example if the user has forgotten their password). You will be prompted to enter and confirm a new password for the user. |
If a display name or ID includes non alphanumeric characters (e.g. a space) then you must enclose it in quote marks. You must also enclose a display name or ID in quotes if it starts with a numeric character.
Note about Deleting Users and Groups and Reuse of User and Group IDs
If you delete a user account or group, you are recommended not to reuse the ID when creating subsequent users or groups. Due to a known issue, in some cases a new user or group may inherit the permission of the previous user or group, if they share the same user ID.
For this reason, you are recommended not to reuse IDs from previously deleted users and groups when creating new users and groups. The problem only occurs when IDs are reused; you can use the same display name as a previously deleted user or group and the issue will not occur (as long as the ID is different).