Managing users

Use the following command line to create a user:

weka user add <username> <role> [password] [--posix-uid uid] [--posix-gid gid]

Using the weka user whoami command, it is possible to receive information about the current user running the command.

To use the new user credentials, use the WEKA_USERNAME and WEKA_PASSWORD environment variables:

$ WEKA_USERNAME=my_new_user WEKA_PASSWORD=S3cret 1 weka user whoami
2 Username    | Source   | Role
3 ------------+----------+--------
4 my_new_user | Internal | Regular

Use the following command line to change a local user password:

weka user passwd <password> [--username username]

weka user revoke-tokens

Use the following command to revoke internal user access to the system and mounting filesystems:

weka user revoke-tokens <username>

You can revoke the access for LDAP users by changing the user-revocation-attribute defined in the LDAP server configuration.

weka user update

Use the following command line to update a local user:

weka user update <username> [--role role] [--posix-uid uid] [--posix-gid gid]

To delete a user, use the following command line:

weka user delete <username>

When a login is attempted, the user is first searched in the list of internal users, i.e., users created using theweka user add command.

However, if a user does not exist in the Content Software for File system but does exist in an LDAP directory, it is possible to configure the LDAP user directory to the Content Software for File system. This will enable a search for the user in the directory, followed by password verification.

On each successful login, a UserLoggedIn event is issued, containing the username, role and whether the user is an internal or LDAP user.

When a login fails, an "Invalid username or password" message is displayed and a UserLoginFailed event is issued, containing the username and the reason for the login failure.

When users open the GUI, they are prompted to provide their username and password. To pass username and password to the CLI, use the WEKA_USERNAME and WEKA_PASSWORD environment variables.

Alternatively, it is possible to log into the CLI as a specific user using the weka user login <username> <password>command. This will run each CLI command from that user. When a user logs in, a token file is created to be used for authentication (default to ~/.weka/auth-token.json, which can be changed using the --path attribute). To see the logged-in CLI user, run theweka user whoami command.

To authenticate users from an LDAP user directory, the LDAP directory must first be configured to theContent Software for File system. This is performed as follows.