Authentication via local accounts
Local accounts are the default authentication method for Allure TestOps. Unlike other methods, it does not rely on any external identity provider and stores everything it needs inside the Allure UAA service's database.
For both the invitations and the password resets, Allure TestOps also needs valid SMTP credentials.
How it works
To log into Allure TestOps, a user enters their credentials: a username and a password.
New users can be registered in two different ways.
An admin can send an invitation link to an email address, thus pre-approving a future account with that address. When sending the invite, the admin specifies which role will be assigned to the new user. See Members § Manage invites for more details.
A user can initiate the registration process of a new account themselves from the registration form. Depending on the configuration, such an account may or may not need approval from an admin. Also, the configuration specifies which role will be assigned to the new account.
This workflow is disabled by default.
Allure TestOps also provides a "Reset password" function.
Parameters
Edit the following parameters in the values.yaml file.
auth.defaultRole
— the role to set for newly registered users. Allowed values: “ROLE_ADMIN”, “ROLE_USER”, “ROLE_GUEST”.
The following parameters exist for compatibility purposes and could lead to security issues and licence overconsumption if auth.defaultRole
is not set to “ROLE_GUEST”. We do not recommend changing these.
registrationEnabled
— iftrue
, users will be able to initiate registration process themselves.autoApprove
— iftrue
, newly registered users will not need approval from administrator.
Edit the following parameters in the .env file.
ALLURE_REGISTRATION_DEFAULT_ROLE
— the role to set for newly registered users. Allowed values: “ROLE_ADMIN”, “ROLE_USER”, “ROLE_GUEST”.
The following parameters exist for compatibility purposes and could lead to security issues and licence overconsumption if ALLURE_REGISTRATION_DEFAULT_ROLE
is not set to “ROLE_GUEST”. We do not recommend changing these.
ALLURE_REGISTRATION_ENABLED
— iftrue
, users will be able to initiate registration process themselves.ALLURE_REGISTRATION_AUTOAPPROVE
— iftrue
, newly registered users will not need approval from administrator.
Edit the following parameters in the /opt/allure-testops/conf/allure-testops.conf file.
ALLURE_REGISTRATION_DEFAULT_ROLE
— the role to set for newly registered users. Allowed values: “ROLE_ADMIN”, “ROLE_USER”, “ROLE_GUEST”.
The following parameters exist for compatibility purposes and could lead to security issues and licence overconsumption if ALLURE_REGISTRATION_DEFAULT_ROLE
is not set to “ROLE_GUEST”. We do not recommend changing these.
ALLURE_REGISTRATION_ENABLED
— iftrue
, users will be able to initiate registration process themselves.ALLURE_REGISTRATION_AUTOAPPROVE
— iftrue
, newly registered users will not need approval from administrator.
Example
registrationEnabled: false
autoApprove: false
auth:
primary: system
defaultRole: ROLE_GUEST
ALLURE_REGISTRATION_ENABLED=false
ALLURE_REGISTRATION_AUTOAPPROVE=false
ALLURE_REGISTRATION_DEFAULT_ROLE=ROLE_GUEST
ALLURE_REGISTRATION_ENABLED=false
ALLURE_REGISTRATION_AUTOAPPROVE=false
ALLURE_REGISTRATION_DEFAULT_ROLE=ROLE_GUEST