Manage user accounts with scripts (on-premises)
The User Management tool enables you to perform user-related tasks on the UFT Mobile database. This section is relevant only for on-premises deployments of UFT Mobile.
The User Management tool allows you to perform the following actions:
- Assign administrator permissions to an existing user*
- Create a new administrator*
- Change or reset an existing user's password*.
Note that when shared spaces are enabled, passwords should be reset from the Operator console. For details, see Shared space management (on-premises). Users can also change their own passwords from the user drop-down menu in the masthead.
- Import users from a file
- Disable SAML SSO
Switch from Device Hours to Concurrent Devices license mode. Note that you need to restart the server for the switch to take effect.
- When using the shared spaces feature: Create a new operator or assign operator permissions to an existing user.
* Note: These options are supported for LDAP only when the username is an email.
Running the User Management tool
You run the User Management tool from the Windows or Linux command line.
To run the User Management tool:
Make sure that you are a root, mc, or UFTMadmin user.
- For Windows, under the UFT Mobile installation, make sure you have admin privileges. Navigate to the server\bin folder and run
For Linux, change directory to your UFT Mobile installation's server/bin directory and run
- Select the task you want to perform and press Enter.
When creating passwords, make sure to follow the following guidelines: The password must be 6-20 characters, and include at least one uppercase English character, one lowercase English character, and one digit.
Note: After an administrator resets a password, for example when it was forgotten, the user will still need to wait the default locking time interval of 15 minutes before logging in again.
You can run the User Management to import users listed in a text file.
To import users:
- Make sure you have an admin execution token for authentication. For details, see Access key management.
Create a text file containing the user information. Each user should be on a new line with the fields separated by semicolons, with the following values:
- Username. The user name, or in database mode (not LDAP/SSO) an email, for example, firstname.lastname@example.org
Password. A password following the guidelines describes above. For LDAP/SSO mode, leave this value blank. If you enter a value, it will be ignored. If the user already exists, their password will not be changed.
- Workspace (optional). A list of workspace names separated by commas. If empty, the user will be assigned to the default workspace.
- Role (optional). One of these values: user , admin, or ws admin. If you do not specify a value, the user will get a non-admin User role. The default value is No.
The following table shows sample user entries.
email@example.com; my_pwd; workspace1; User
Valid: A regular user is assigned to workspace1
tom; my_pwd; workspace1; User
Invalid: Wrong user name
firstname.lastname@example.org; my_pwd; ;
Valid: A regular user is assigned to the default workspace
email@example.com; my_pwd; ;userrole
Invalid. The specified role type is wrong.
Run the script as described above and specify the import option.
- Enter the admin's execution token.
- Enter the path to a text file with the user information.
- Indicate whether or not to overwrite existing user roles and workspaces.
- The script console indicates the number of records that succeeded and failed. Check the log file, userOnboarding.log in the Logs folder for details.
Note: When loading users from a file while in LDAP mode, the results will always show zero users added, even if new users were actually added.