TABLE OF CONTENTS

• Problem
• Solutions
  • For Allure TestOps versions earlier than 4.26.5
    • Docker compose
    • Helm chart
  • Allure TestOps 5.x.x and newer releases
    • Docker compose
    • Helm chart

Problem

The person who has deployed Allure TestOps on-premises was only administrator and has left the company. No one knows the credentials of the administrator of Allure TestOps instance. The rest of the team has only the role User or Guest.

How can we restore administrative access to the Allure TestOps instance?

Solutions

Your actions depend on the version you have currently deployed in your infrastruccture.

For Allure TestOps versions earlier than 4.26.5

Depending on your deployment type, you need to locate the credentials of the first admin user:

Docker compose

For Docker Compose, these parameters are stored in .env:

# Standard Admin's Login name. This user allows you restoring the access to Allure TestOps
ALLURE_ADMIN=admin

# Update this before deployment
ALLURE_ADMIN_PASS=admin

Helm chart

For Kubernetes, they can be found in values.yaml:

## Credentials for accessing AllureTestOps as Admin on default auth scheme
username: admin
password: admin

These fields contain the login credentials for the initial admin user. This user acts as the root account and is required for managing licenses. All license-related operations can only be performed by this account.

Allure TestOps 5.x.x and newer releases

In newer versions of TestOps, the creation of the first admin has changed and now requires a properly configured SMTP server, since the first account is created via invitation email.

If you've lost access to the initial admin, locate the following parameters:

Docker compose

For Docker Compose, check .env:

########################################################################################
# FIRST_ADMIN_EMAIL
# The email address configured below (FIRST_ADMIN_EMAIL) will be used by the system
# to send the invitation to the very first administrator of the instance.
# For the operation to complete successfully, all SMTP_ parameters must be configured.
########################################################################################
FIRST_ADMIN_EMAIL=testops-first-admin@company.test

Helm chart

For Kubernetes, check values.yaml:

############################################################################################################
# Email address of the very first user of TestOps instance to send the invitation.
# This is the first admin of the system who will invite other users.
# Make sure SMTP parameters are set to send the invite.
############################################################################################################
email: you@company.com

The email field defines the address of the first admin user who manages licensing.

• If this email is still valid, you can reset the password and log in.

• If it’s deactivated, you can reactivate it and log in, or update the value with a new email (important: the new email must not belong to an existing account). Then, set a password and log in.

⚠️ Starting from version 5.x.x, the root admin has the same permissions as other administrator accounts in your instance.