Setup test users¶
A test user is a dummy user set up for the automation to use when logging in to your environments.
IT needs to create the accounts first
The accounts themselves are created in your tenant by your IT team, along with any network and MFA configuration. That's covered in IT access requirements. Share it with them before you get to this page.
Never use a real person's identity
Test users must be dedicated accounts. A real person's credentials in an automated test means locked accounts, unattributable activity and an audit problem.
Add a test user¶
- Select your application.
- Open the Authentication tab to view and add test users.
- Click Add. A dialog appears with several options:
| Field | Notes |
|---|---|
| The test account's sign-in address | |
| Password | Not readable in the dialog once submitted |
| Description | Use this as a label |
| Secret Key | The secret key provided during Microsoft login, used when setting up MFA. elevaite365 uses its own TOTP logic, so software OATH/TOTP must be enabled for the account, see IT access requirements |
Once submitted, your new user displays in the table.
Default user¶
On the far right of the table there's an option to select the default application for the user.
For Microsoft applications, this user pre-fills the login command, so whenever a new test is created the login defaults to that user.
If sign-in fails for this user
Nine times in ten it's tenant configuration rather than the test: the account isn't excluded from phone registration, software OATH/TOTP isn't enabled, Conditional Access is blocking the sign-in, or our regional IPs aren't allowlisted. All four are covered in IT access requirements.
Next: Create components