### Install RabbitMQ

Source: https://docs.qameta.io/allure-testops/server/install/linux-packages/deb

Commands to install RabbitMQ server on Debian-based systems. Includes downloading the Erlang setup script, installing dependencies, downloading the RabbitMQ .deb package, and enabling/starting the service.

```bash
wget -q -O- https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-erlang/setup.deb.sh | sudo bash
sudo apt install -y socat logrotate erlang
wget https://github.com/rabbitmq/rabbitmq-server/releases/download/v3.13.2/rabbitmq-server_3.13.2-1_all.deb -O rabbitmq-server.deb
sudo dpkg -i rabbitmq-server.deb
sudo systemctl enable rabbitmq-server
sudo systemctl start rabbitmq-server
```

--------------------------------

### Example output of docker compose ps

Source: https://docs.qameta.io/allure-testops/server/upgrade/archive/v4-docker-compose-installation

Example output showing service names, statuses, and ports. The SERVICE column is used to get logs for specific components.

```text
name@computer folder-name % docker compose ps
NAME                 COMMAND                  SERVICE                    STATUS               PORTS
allure-gateway       "/bin/sh -c /entrypo…"   allure-gateway             running (healthy)   0.0.0.0:10777->8080/tcp
allure-report        "/bin/sh -c /entrypo…"   allure-report              running (healthy)
allure-uaa           "/bin/sh -c /entrypo…"   allure-uaa                 running (healthy)
autoheal             "/docker-entrypoint …"   autoheal                   running (healthy)
minio-local          "/opt/bitnami/script…"   minio-local                running              0.0.0.0:9000->9000/tcp
minio-provisioning   "/bin/sh -c 'mc conf…"   minio-local-provisioning   exited (0)
rabbit               "/opt/bitnami/script…"   rabbitmq                   running              25672/tcp
redis                "/opt/bitnami/script…"   redis                      running (healthy)    6379/tcp
report-db            "docker-entrypoint.s…"   report-db                  running              5432/tcp
uaa-db               "docker-entrypoint.s…"   uaa-db                     running              5432/tcp

```

--------------------------------

### Install PostgreSQL 15

Source: https://docs.qameta.io/allure-testops/server/install/linux-packages/rpm

Installs PostgreSQL 15 server, initializes the database, and enables/starts the service.

```bash
sudo yum install -y https://download.postgresql.org/pub/repos/yum/reporpms/EL-$(rpm -E %{rhel})-$(arch)/pgdg-redhat-repo-latest.noarch.rpm
sudo dnf -y module disable postgresql
sudo yum install -y postgresql15-server
sudo /usr/pgsql-15/bin/postgresql-15-setup initdb
sudo systemctl enable postgresql-15
sudo systemctl start postgresql-15
```

--------------------------------

### Start Allure TestOps services

Source: https://docs.qameta.io/allure-testops/server/install/linux-packages/deb

Use this command to start all Allure TestOps services after installation or when they are stopped.

```bash
sudo systemctl start testops

```

--------------------------------

### Example: Save logs for testops service

Source: https://docs.qameta.io/server/install/docker-compose

Example command to save logs for the 'testops' service to 'testops.log'.

```bash
docker compose logs testops > testops.log
```

--------------------------------

### Install RabbitMQ (optional)

Source: https://docs.qameta.io/allure-testops/server/upgrade/archive/v4-rpm-installation

Installs RabbitMQ server on the same machine as Allure TestOps. Not recommended for high-load use cases.

```bash
curl -1sLf 'https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-erlang/setup.rpm.sh' | sudo bash
sudo yum install -y socat logrotate initscripts erlang
sudo yum install -y https://github.com/rabbitmq/rabbitmq-server/releases/download/v3.9.14/rabbitmq-server-3.9.14-1.el8.noarch.rpm
sudo chkconfig rabbitmq-server on
sudo /sbin/service rabbitmq-server start

```

--------------------------------

### Launch AQL function examples

Source: https://docs.qameta.io/allure-testops/reference/aql

Examples of launch AQL functions for dynamic values in widget queries. Each function returns a timestamp or user value for comparison in AQL expressions.

```aql
createdDate > dayStartUtc()
```

```aql
createdDate > weekAgo()
```

```aql
createdDate > twoWeeksAgo()
```

```aql
createdDate > threeMonthsAgo()
```

```aql
createdDate > sixMonthsAgo()
```

```aql
createdBy = currentUser()
```

--------------------------------

### AQL launch function: createdDate > dayStartUtc()

Source: https://docs.qameta.io/reference/aql

Use dayStartUtc() to get today's day start as an epoch UTC time stamp. The example filters launches created after the start of today.

```aql
createdDate > dayStartUtc()
```

--------------------------------

### Install the VS Code extension via command line

Source: https://docs.qameta.io/allure-testops/reference/ecosystem/vs-code-plugin

Install the qameta.allure-vscode extension from the VS Code marketplace or by using the command palette (Ctrl+P) and pasting this command.

```shell
ext install qameta.allure-vscode

```

--------------------------------

### Complete SAML2 configuration example for testops.conf

Source: https://docs.qameta.io/allure-testops/server/configure/authentication/saml/okta-saml-2-0

Example environment variables for enabling SAML2 with Okta. Set ALLURE_LOGIN_PRIMARY to 'system' initially for testing, and use ROLE_GUEST as default role when syncRoles is true.

```properties
ALLURE_LOGIN_PRIMARY=system
ALLURE_LOGIN_SAML2_ENABLED=true
ALLURE_LOGIN_SAML2_ID=okta
ALLURE_LOGIN_SAML2_ACS_URL=https://testops.xyz/api/login/saml2/sso/{registrationId}
ALLURE_LOGIN_SAML2_ENTITY_ID=https://testops.xyz/api/login/saml2/authenticate/{registrationId}
ALLURE_LOGIN_SAML2_METADATA_URL=https://trial-000000.okta.com/app/eXXXXXXXXXXXXXXXX7/sso/saml/metadata
ALLURE_LOGIN_SAML2_DEFAULTROLE=ROLE_GUEST
ALLURE_LOGIN_SAML2_FIRSTNAMEATTRIBUTE=firstName
ALLURE_LOGIN_SAML2_LASTNAMEATTRIBUTE=lastName
ALLURE_LOGIN_SAML2_EMAILATTRIBUTE=email
ALLURE_LOGIN_SAML2_SYNCROLES=true
ALLURE_LOGIN_SAML2_GROUPROLEATTRIBUTE=groups
ALLURE_LOGIN_SAML2_GROUPAUTHORITIES_ROLEUSERGROUPS=ato_users
ALLURE_LOGIN_SAML2_GROUPAUTHORITIES_ROLEADMINGROUPS=ato_admins
```

--------------------------------

### List all installed components in the testops namespace

Source: https://docs.qameta.io/allure-testops/server/install/kubernetes

Use this command to get the list of all installed components in the 'testops' namespace, which is the first step in collecting debug information.

```bash
kubectl get all -n testops

```

--------------------------------

### Install PostgreSQL 15

Source: https://docs.qameta.io/allure-testops/server/install/linux-packages/deb

Adds the PostgreSQL apt repository and installs postgresql-15. This is optional for high-load use cases but can be run on the same machine.

```bash
wget -q -O- https://www.postgresql.org/media/keys/ACCC4CF8.asc | sudo gpg --dearmor --output /usr/share/keyrings/pgdg.gpg
echo "deb [signed-by=/usr/share/keyrings/pgdg.gpg] http://apt.postgresql.org/pub/repos/apt $(lsb_release -cs)-pgdg main" | sudo tee /etc/apt/sources.list.d/pgdg.list
sudo apt update
sudo apt install -y postgresql-15

```

--------------------------------

### AQL launch function: createdDate > twoWeeksAgo()

Source: https://docs.qameta.io/reference/aql

Use twoWeeksAgo() to get the UTC epoch time stamp back 2 weeks from now. The example returns everything created during the last 2 weeks.

```aql
createdDate > twoWeeksAgo()
```

--------------------------------

### Install PostgreSQL 15

Source: https://docs.qameta.io/server/install/linux-packages/rpm

Commands to install PostgreSQL 15 on the same machine as Allure TestOps (not recommended for high-load use cases).

```bash
sudo yum install -y https://download.postgresql.org/pub/repos/yum/reporpms/EL-$(rpm -E %{rhel})-$(arch)/pgdg-redhat-repo-latest.noarch.rpm
sudo dnf -y module disable postgresql
sudo yum install -y postgresql15-server
sudo /usr/pgsql-15/bin/postgresql-15-setup initdb
sudo systemctl enable postgresql-15
sudo systemctl start postgresql-15

```

--------------------------------

### Configuration file example

Source: https://docs.qameta.io/allure-testops/reference/ecosystem/allurectl

Shows the content of an allurectl configuration file (default location ~/.allure/config.yaml) with the endpoint parameter.

```yaml
endpoint: https://your-testops.example.com

```

--------------------------------

### AQL launch function: createdDate > threeMonthsAgo()

Source: https://docs.qameta.io/reference/aql

Use threeMonthsAgo() to get the UTC epoch time stamp back 3 months from now. The example returns everything created during the last 3 months.

```aql
createdDate > threeMonthsAgo()
```

--------------------------------

### Install Redis

Source: https://docs.qameta.io/allure-testops/server/install/linux-packages/rpm

Command to install Redis using yum.

```bash
sudo yum install -y redis
```

--------------------------------

### AQL launch function: createdDate > sixMonthsAgo()

Source: https://docs.qameta.io/reference/aql

Use sixMonthsAgo() to get the UTC epoch time stamp back 6 months from now. The example returns everything created during the last 6 months.

```aql
createdDate > sixMonthsAgo()
```

--------------------------------

### upload example with command line parameters

Source: https://docs.qameta.io/allure-testops/reference/ecosystem/allurectl

Runs allurectl upload with all required parameters provided as command-line flags, including endpoint, token, project ID, launch name, tags, and the results directory.

```bash
./allurectl upload \
  --endpoint https://testops.example.com \
  --token 55555555-5555-5555-5555-555555555555 \
  --project-id 100 \
  --launch-name "Local verification run" \
  --launch-tags "regress, nightly" \
  /path/to/allure-results

```

--------------------------------

### Install Amazon Corretto 17

Source: https://docs.qameta.io/allure-testops/server/upgrade/archive/v4-rpm-installation

Adds the Corretto repository and installs java-17-amazon-corretto-devel, the JDK used for Allure TestOps.

```bash
curl -1sLf https://yum.corretto.aws/corretto.repo | sudo tee /etc/yum.repos.d/corretto.repo
sudo yum install -y java-17-amazon-corretto-devel

```

--------------------------------

### Install PostgreSQL 14 (optional)

Source: https://docs.qameta.io/allure-testops/server/upgrade/archive/v4-deb-installation

Commands to install PostgreSQL 14 on the same machine as Allure TestOps. Not recommended for high-load use cases.

```bash
wget -q -O- https://www.postgresql.org/media/keys/ACCC4CF8.asc | sudo gpg --dearmor --output /usr/share/keyrings/pgdg.gpg
echo "deb [signed-by=/usr/share/keyrings/pgdg.gpg] http://apt.postgresql.org/pub/repos/apt $(lsb_release -cs)-pgdg main" | sudo tee /etc/apt/sources.list.d/pgdg.list
sudo apt update
sudo apt install -y postgresql-14

```

--------------------------------

### Configure local authentication with SMTP

Source: https://docs.qameta.io/allure-testops/server/upgrade/archive/v4-kubernetes-installation

Example for local accounts authentication. Requires SMTP to be configured. This example is illustrative and won't work without changes.

```yaml
# this is just an example which won't work if applied without any changes.
allure:
  auth:
    primary: system
smtp:
  enabled: true
  host: smtp.gmail.com
  port: 465
  authEnabled: true
  from: noreply@yourcompany.com
  username: serice-account-for-SMTP
  password: SMPTPasswordOrAppPasswordOrAnyOtherSecretRequiredBySMTP
  startTLSEnabled: true
  startTLSRequired: true
  sslEnabled: true
  sslTrust: smtp.gmail.com

```

--------------------------------

### Install Allure TestOps package

Source: https://docs.qameta.io/allure-testops/server/install/linux-packages/deb

Installs the testops package using apt.

```bash
sudo apt install -y testops
```

--------------------------------

### watch example with command line parameters

Source: https://docs.qameta.io/allure-testops/reference/ecosystem/allurectl

Runs allurectl watch with all required parameters provided as command-line flags, including endpoint, token, project ID, launch name, tags, and results path.

```bash
./allurectl watch \
  --endpoint https://testops.example.com \
  --token 55555555-5555-5555-5555-555555555555 \
  --project-id 100 \
  --launch-name "Local verification run" \
  --launch-tags "regress,nightly" \
  --results path/to/allure-results \
  -- /path/to/tests/execution/command

```

--------------------------------

### SMTP configuration example for allure-uaa.conf

Source: https://docs.qameta.io/allure-testops/server/upgrade/archive/v4-deb-installation

Example SMTP configuration for the allure-uaa.conf file. This is an example and will not work without updating with real SMTP server data.

```properties
# please remember, this is an example, which won't work for you,
# you need to update your config with real SMTP server data.
ALLURE_MAIL_HOST=smtp.gmail.com
ALLURE_MAIL_PORT=465
ALLURE_MAIL_USERNAME=username
ALLURE_MAIL_PASSWORD=password
ALLURE_MAIL_FROM=noreply@example.com
ALLURE_MAIL_SMTP_AUTH=true
ALLURE_MAIL_SMTP_STARTTLS_ENABLE=true
ALLURE_MAIL_SMTP_STARTTLS_REQUIRED=true
ALLURE_MAIL_SMTP_SSL_ENABLE=true
ALLURE_MAIL_SMTP_SSL_TRUST=smtp.gmail.com

```

--------------------------------

### List installed components with kubectl

Source: https://docs.qameta.io/allure-testops/server/upgrade/archive/v4-kubernetes-installation

Retrieves the list of all installed components in the cluster, useful for identifying Allure TestOps resources.

```bash
kubectl get all

```

--------------------------------

### testplan.json example

Source: https://docs.qameta.io/allure-testops/reference/ecosystem/allurectl

Example testplan.json file with version and tests array containing id and selector fields. The id is the Allure ID from TestOps, and the selector is a test-framework-specific selector.

```json
{
  "version": "1.0",
  "tests": [
    {
      "id": "10",
      "selector": "io.qameta.allure.examples.junit4.AllureSimpleTest.allureSimpleTest"
    },
    {
      "id": "11",
      "selector": "io.qameta.allure.examples.junit4.AllureParameterizedTest.allureParameterizedTest[First Name]"
    }
  ]
}
```

--------------------------------

### Environment variables example for upload

Source: https://docs.qameta.io/allure-testops/reference/ecosystem/allurectl

Sets the required environment variables (ALLURE_ENDPOINT, ALLURE_TOKEN, ALLURE_PROJECT_ID, ALLURE_LAUNCH_NAME) and runs allurectl upload to upload results from a specified directory.

```bash
# defined somewhere in the pipeline
export ALLURE_ENDPOINT=https://testops.example.com
export ALLURE_TOKEN=55555555-5555-5555-5555-555555555555
export ALLURE_PROJECT_ID=100
export ALLURE_LAUNCH_NAME="Nightly API tests"

# tests executed somewhere
# results are copied from somewhere to /path/to/allure-results

# uploading results
./allurectl upload /path/to/allure-results

```

--------------------------------

### Install Allure TestOps box package

Source: https://docs.qameta.io/allure-testops/server/upgrade/archive/v4-deb-installation

Installs the 'box' option of Allure TestOps, which automatically installs MinIO, Redis, and RabbitMQ locally. Assumes PostgreSQL is installed locally.

```bash
sudo apt install -y allure-testops-box

```

--------------------------------

### DEB/RPM SMTP configuration in testops.conf

Source: https://docs.qameta.io/allure-testops/server/configure/smtp

Edit these values in /opt/testops/conf/testops.conf to configure SMTP for DEB/RPM deployments. The example shows a typical authenticated SMTP setup with host, port, authentication, sender address, and TLS settings. Replace placeholders with your own mail host, account, and secret values.

```properties
SPRING_MAIL_HOST=smtp.example.com
SPRING_MAIL_PORT=587
SPRING_MAIL_USERNAME=noreply@example.com
SPRING_MAIL_PASSWORD=<smtp-password>
ALLURE_MAIL_FROM=noreply@example.com
SPRING_MAIL_PROPERTIES_MAIL_SMTP_AUTH=true
SPRING_MAIL_PROPERTIES_MAIL_SMTP_STARTTLS_ENABLE=true
SPRING_MAIL_PROPERTIES_MAIL_SMTP_STARTTLS_REQUIRED=true
SPRING_MAIL_PROPERTIES_MAIL_SMTP_SSL_ENABLE=true
SPRING_MAIL_PROPERTIES_MAIL_SMTP_SSL_TRUST=smtp.example.com

```

--------------------------------

### Install Allure TestOps package

Source: https://docs.qameta.io/allure-testops/server/install/linux-packages/rpm

Installs the testops package. Replace 26.1.1 with the desired version.

```bash
sudo yum install -y testops-26.1.1
```

--------------------------------

### Install Allure TestOps min package

Source: https://docs.qameta.io/allure-testops/server/upgrade/archive/v4-deb-installation

Installs the 'min' option of Allure TestOps, which only installs Allure TestOps itself.

```bash
sudo apt install -y allure-testops-min

```

--------------------------------

### Install Redis

Source: https://docs.qameta.io/allure-testops/server/install/linux-packages/deb

Commands to install Redis on Debian-based systems. Adds the Redis repository, updates package lists, and installs the redis package.

```bash
wget -q -O- https://packages.redis.io/gpg | sudo gpg --dearmor --output /usr/share/keyrings/redis-archive-keyring.gpg
echo "deb [signed-by=/usr/share/keyrings/redis-archive-keyring.gpg] https://packages.redis.io/deb $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/redis.list
sudo apt update
sudo apt install -y redis
```

--------------------------------

### Navigate to installation directory

Source: https://docs.qameta.io/allure-testops/server/install/docker-compose

Change to the Allure TestOps installation directory, typically ~/testops, before running Docker Compose commands.

```bash
cd ~/testops
```

--------------------------------

### Install RabbitMQ

Source: https://docs.qameta.io/allure-testops/server/install/linux-packages/rpm

Commands to install RabbitMQ and its dependencies. Note that versions below 26.2.1.4 do not support quorum queues in high-availability mode for RabbitMQ 4.0+; use RabbitMQ 3.x if high availability is required.

```bash
wget -q -O- https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-erlang/setup.rpm.sh | sudo bash
sudo yum install -y socat logrotate initscripts erlang
sudo yum install -y https://github.com/rabbitmq/rabbitmq-server/releases/download/v3.13.2/rabbitmq-server-3.13.2-1.el8.noarch.rpm
sudo chkconfig rabbitmq-server on
sudo /sbin/service rabbitmq-server start
```

--------------------------------

### Full output of allurectl job-run env

Source: https://docs.qameta.io/allure-testops/reference/ecosystem/allurectl

Example output of the 'allurectl job-run env' command, showing the environment variables and their values.

```bash
ALLURE_LAUNCH_ID=646248
ALLURE_LAUNCH_URL=https://demo.testops.cloud/launch/646248
ALLURE_JOB_RUN_ID=600760
ALLURE_TESTOPS_JOB_RUN_URL=https://demo.testops.cloud/jobrun/600760

```

--------------------------------

### Install Allure TestOps 'box' package

Source: https://docs.qameta.io/allure-testops/server/upgrade/archive/v4-rpm-installation

Installs the 'box' package of Allure TestOps. Replace 4.22.1 with the desired version. This automatically installs MinIO and Redis locally.

```bash
sudo yum install -y allure-testops-box-4.22.1
```

--------------------------------

### Azure AD OpenID configuration in values.yaml

Source: https://docs.qameta.io/allure-testops/server/configure/authentication/openid/azure-ad

Example YAML configuration for the auth.openid section in values.yaml. It is a template and will not work without replacing placeholders like <your-client-id> and <tenant-id>. The example includes commented-out userinfoUri and issuerUri fields.

```yaml
# This is an example that will not work if applied without any changes.
auth:
  primary: openid
  # ...
  openid:
    enabled: false
    providerName: azure
    clientName: testops
    clientId: <your-client-id>
    clientSecret: <your-client-secret>
    redirectUri: https://testops.example.com/login/oauth2/code/azure
    scope: openid, email, profile
    authorizationGrantType: authorization_code
    authorizationUri: https://login.microsoftonline.com/<tenant-id>/oauth2/v2.0/authorize
    jwksSetUri: https://login.microsoftonline.com/<tenant-id>/discovery/v2.0/keys
    tokenUri: https://login.microsoftonline.com/<tenant-id>/oauth2/v2.0/token
    usernameAttribute: preferred_username
    defaultRole: ROLE_GUEST
    syncRoles: false
    groupRoleAttribute: groupRoleAttribute
    roleUserGroups: roleUserGroups
    roleAdminGroups: roleAdminGroups
    # userinfoUri: https://graph.microsoft.com/oidc/userinfo
    userinfoUri:
    # issuerUri: https://login.microsoftonline.com/a411f6bf-a08d-4aab-bef9-7f0991b2ec76/v2.0
    issuerUri: 
    firstNameAttribute:
    lastNameAttribute:

```

--------------------------------

### Install Amazon Corretto 21 JDK

Source: https://docs.qameta.io/allure-testops/server/install/linux-packages/deb

Adds the Corretto repository and installs java-21-amazon-corretto-jdk, which is used as the JDK implementation for Allure TestOps.

```bash
wget -q -O- https://apt.corretto.aws/corretto.key | sudo gpg --dearmor --output /usr/share/keyrings/corretto.gpg
echo "deb [signed-by=/usr/share/keyrings/corretto.gpg] https://apt.corretto.aws stable main" | sudo tee /etc/apt/sources.list.d/corretto.list
sudo apt update
sudo apt install -y java-21-amazon-corretto-jdk

```

--------------------------------

### Example ldapsearch output

Source: https://docs.qameta.io/allure-testops/server/configure/authentication/ldap

Example output from the ldapsearch command, showing group attributes and memberUid values.

```text
dn: cn=admins,ou=Groups,dc=example,dc=org
objectClass: posixGroup
objectClass: top
cn: admins
memberUid: admin
memberUid: john

```

--------------------------------

### Install HashiCorp Consul

Source: https://docs.qameta.io/allure-testops/server/upgrade/archive/v4-deb-installation

Commands to install HashiCorp Consul, used for service discovery and communication between Allure TestOps components.

```bash
wget -q -O- https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor --output /usr/share/keyrings/hashicorp.gpg
echo "deb [arch=amd64 signed-by=/usr/share/keyrings/hashicorp.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/hashicorp.list
sudo apt update
sudo apt install -y consul

```

--------------------------------

### Install Amazon Corretto 17 JDK

Source: https://docs.qameta.io/allure-testops/server/upgrade/archive/v4-deb-installation

Commands to install Amazon Corretto version 17, the JDK implementation used for running Allure TestOps.

```bash
wget -q -O- https://apt.corretto.aws/corretto.key | sudo gpg --dearmor --output /usr/share/keyrings/corretto.gpg
echo "deb [signed-by=/usr/share/keyrings/corretto.gpg] https://apt.corretto.aws stable main" | sudo tee /etc/apt/sources.list.d/corretto.list
sudo apt update
sudo apt install -y java-17-amazon-corretto-jdk

```

--------------------------------

### Start Allure TestOps services

Source: https://docs.qameta.io/allure-testops/server/install/docker-compose

Start the Allure TestOps services in detached mode using Docker Compose.

```bash
docker compose up -d

```

--------------------------------

### Navigate to installation directory

Source: https://docs.qameta.io/allure-testops/server/install/docker-compose

Use this command to change to the Allure TestOps installation directory, e.g., ~/testops, before running Docker Compose commands.

```bash
cd ~/testops

```

--------------------------------

### Start Allure TestOps services

Source: https://docs.qameta.io/allure-testops/server/install/docker-compose

Launch the Docker Compose configuration to start Allure TestOps services in detached mode.

```bash
docker compose up -d
```

--------------------------------

### AQL launch function: createdBy = currentUser()

Source: https://docs.qameta.io/reference/aql

Use currentUser() to return the currently logged in user. The example gives the logged in user all launches created by them.

```aql
createdBy = currentUser()
```

--------------------------------

### LDAP configuration example for allure-uaa.conf

Source: https://docs.qameta.io/allure-testops/server/upgrade/archive/v4-deb-installation

Example LDAP configuration for the allure-uaa.conf file. Includes settings for LDAP login, user search, group search, and service account credentials.

```properties
#Example of using LDAP
ALLURE_LOGIN_PRIMARY=ldap
ALLURE_LOGIN_LDAP_ENABLED='true'
ALLURE_LOGIN_LDAP_REFERRAL=follow
ALLURE_LOGIN_LDAP_URL=ldap://ldap.url.here:port
# ALLURE_LOGIN_LDAP_USERDNPATTERNS= do not use with ALLURE_LOGIN_LDAP_USERSEARCHFILTER
ALLURE_LOGIN_LDAP_USERSEARCHBASE="ou=People,dc=space"
ALLURE_LOGIN_LDAP_USERSEARCHFILTER="uid={0}"
ALLURE_LOGIN_LDAP_DEFAULTROLE=${LDAP_DEFAULT_ROLE}
ALLURE_LOGIN_LDAP_UIDATTRIBUTE=uid
ALLURE_LOGIN_LDAP_SYNCROLES='true'
# these are to be enabled if ALLURE_LOGIN_LDAP_SYNCROLES='true'
ALLURE_LOGIN_LDAP_GROUPSEARCHBASE="ou=group,dc=space"
ALLURE_LOGIN_LDAP_GROUPSEARCHFILTER="memberUid={1}"
ALLURE_LOGIN_LDAP_GROUPROLEATTRIBUTE=cn

ALLURE_LOGIN_LDAP_GROUPAUTHORITIES_ROLEUSERGROUPS=group_with_ato_users,every_user_is_user
ALLURE_LOGIN_LDAP_GROUPAUTHORITIES_ROLEADMINGROUPS=group_with_ato_admins,every_user_is_admin
# service account data to log-in to LDAP
ALLURE_LOGIN_LDAP_USERDN="cn=admin,dc=space"
ALLURE_LOGIN_LDAP_PASSWORD='ServiceAccountPasswordHere'
# additional parameters, can be disabled by default
#ALLURE_LOGIN_LDAP_LOWERCASEUSERNAMES=true
#ALLURE_LOGIN_LDAP_PASSWORDATTRIBUTE=userPassword

```

--------------------------------

### Download allurectl and wrap test command with watch

Source: https://docs.qameta.io/allure-testops/reference/integrations/ci-systems/teamcity

Commands to download the allurectl binary and run tests under its watch mode. Use this when the TeamCity plugin cannot be installed. Adjust the binary URL for different OS/architecture.

```bash
curl -fsSL https://github.com/allure-framework/allurectl/releases/latest/download/allurectl_linux_amd64 -o allurectl
chmod +x allurectl
./allurectl watch -- ./gradlew clean test
```

--------------------------------

### Complete .env configuration

Source: https://docs.qameta.io/allure-testops/server/configure/authentication/saml/okta-saml-2-0

Environment variable configuration for the .env file. Includes LOGIN_SAML2_* variables for Okta SAML setup, with REGISTRATION_DEFAULT_ROLE set to ROLE_GUEST as required when syncRoles is true.

```env
LOGIN_SAML2_ENABLED=true
REGISTRATION_DEFAULT_ROLE=ROLE_GUEST
LOGIN_SAML2_ID=Okta
LOGIN_SAML2_ACS_URL=https://testops.xyz/api/login/saml2/sso/{registrationId}
LOGIN_SAML2_ENTITY_ID=https://testops.xyz/api/login/saml2/authenticate/{registrationId}
LOGIN_SAML2_METADATA_URL=https://trial-0000000.okta.com/app/eXXXXXXXXXXXXXXXX7/sso/saml/metadata
LOGIN_SAML2_FIRSTNAMEATTRIBUTE=firstName
LOGIN_SAML2_LASTNAMEATTRIBUTE=lastName
LOGIN_SAML2_EMAILATTRIBUTE=email
LOGIN_SAML2_SYNCROLES=true
LOGIN_SAML2_GROUPROLEATTRIBUTE=groups
LOGIN_SAML2_GROUPAUTHORITIES_ROLEUSERGROUPS=ato_users
LOGIN_SAML2_GROUPAUTHORITIES_ROLEADMINGROUPS=ato_admins

```

--------------------------------

### Combine conditions with AND

Source: https://docs.qameta.io/allure-testops/reference/aql

Use the 'and' keyword to require multiple conditions. This example finds test cases with 'test' in the name created by John.

```aql
name ~= "test" and createdBy = "John"
```

--------------------------------

### ldapsearch output example

Source: https://docs.qameta.io/allure-testops/server/configure/authentication/ldap

Example output from the ldapsearch command, showing an LDAP entry for user John Doe with attributes including objectClass, cn, givenName, sn, mail, and uid.

```text
dn: cn=John Doe,ou=People,dc=example,dc=org
objectClass: inetOrgPerson
objectClass: posixAccount
objectClass: person
cn: John Doe
givenName: John
sn: Doe
mail: john.doe@email.com
uid: john
```

--------------------------------

### Complete GitHub Action workflow example for Allure TestOps

Source: https://docs.qameta.io/reference/integrations/ci-systems/github

Full workflow example that runs tests and uploads results to TestOps. Includes `workflow_dispatch` inputs and `env` configuration. The `ALLURE_JOB_RUN_ID` is used to upload into an existing launch when present.

```yaml
name: run-and-upload-to-testops

on:
  workflow_dispatch:
    inputs:
      TESTS_BROWSER:
        description: "Browser to be used in tests"
        required: true
        default: chrome
      ALLURE_JOB_RUN_ID:
        description: "Allure TestOps service parameter. Leave blank."
        required: false
      ALLURE_USERNAME:
        description: "Allure TestOps service parameter. Leave blank."
        required: false

env:
  ALLURE_RESULTS: allure-results
  ALLURE_JOB_RUN_ID: ${{ github.event.inputs.ALLURE_JOB_RUN_ID }}
```

--------------------------------

### Configure LDAP authentication

Source: https://docs.qameta.io/allure-testops/server/upgrade/archive/v4-kubernetes-installation

Example for LDAP authentication. Includes LDAP server URL, user/group search filters, and role mapping. Note that 'enabled' is set to false in this example.

```yaml
allure:
  auth:
    primary: ldap
    ldap:
      enabled: false
      auth:
        user: user
        pass: pass
      referral: follow
      url: ldap://ldap.example.com:389
      usernamesToLowercase: true
      passwordAttribute: userPassword
      user:
        searchBase: dc=example,dc=com
        searchFilter: (&((objectClass=Person))(uid={0}))
      syncRoles: false
      uidAttribute: uid
      group:
        searchBase: ou=qa,ou=Security Groups,dc=example,dc=com
        searchFilter: (&(objectClass=Person)(uid={1}))
        roleAttribute: cn
      userGroupName: allure_users
      adminGroupName: allure_admins

```

--------------------------------

### Install Allure TestOps with Helm

Source: https://docs.qameta.io/allure-testops/server/upgrade/archive/v4-kubernetes-installation

Installs Allure TestOps using the Helm chart and configured values.yaml. The --set overrides disable readiness and liveness probes to prevent Kubernetes from killing services during initialization. This measure is also needed during upgrades.

```bash
helm install allure-testops qameta/allure-testops --values values.yaml --set readinessProbe.enabled=false --set livenessProbe.enabled=false

```

--------------------------------

### DEB/RPM testops.conf HTTPS configuration

Source: https://docs.qameta.io/allure-testops/server/configure/network-and-https

Update ALLURE_ENDPOINT to use https instead of http in /opt/testops/conf/testops.conf. This example shows the required parameter for enabling HTTPS in DEB or RPM installations.

```properties
ALLURE_ENDPOINT=https://testops.example.com

```

--------------------------------

### Set TestOps URL parameters in .env

Source: https://docs.qameta.io/allure-testops/server/upgrade/archive/v4-docker-compose-installation

Example .env parameters to set the Allure TestOps instance URL to http://testops.example.com/ using port 80. Adjust ALLURE_PROTO, ALLURE_HOST, and ALLURE_INSTANCE_PORT as needed.

```plaintext
ALLURE_PROTO=http
ALLURE_HOST=testops.example.com
ALLURE_INSTANCE_PORT=80

```

--------------------------------

### Docker Compose .env HTTPS configuration

Source: https://docs.qameta.io/allure-testops/server/configure/network-and-https

Update TESTOPS_PROTO to https and TESTOPS_INSTANCE_PORT to 443. This example shows the required environment variables for enabling HTTPS in a Docker Compose installation.

```env
TESTOPS_PROTO=https
TESTOPS_INSTANCE_URL=testops.example.com
TESTOPS_INSTANCE_PORT=443
TESTOPS_CONTAINER_PORT=8080

```

--------------------------------

### Configure Docker registry and repository for Allure TestOps

Source: https://docs.qameta.io/allure-testops/server/install/docker-compose

Define the IMAGES_REGISTRY and IMAGES_REPO parameters to pull images from the Qameta Software private registry. The example uses docker.io and allure.

```bash
IMAGES_REGISTRY=docker.io
IMAGES_REPO=allure

```

--------------------------------

### AQL launch function: createdDate > weekAgo()

Source: https://docs.qameta.io/reference/aql

Use weekAgo() to get the UTC epoch time stamp back 1 week from now. The example returns everything created during the last week.

```aql
createdDate > weekAgo()
```

--------------------------------

### GitHub Actions workflow with allurectl watch

Source: https://docs.qameta.io/allure-testops/reference/integrations/ci-systems/github

Workflow that installs allurectl via the setup-allurectl action and runs tests with allurectl watch. Requires ALLURE_ENDPOINT, ALLURE_PROJECT_ID, ALLURE_RESULTS, and ALLURE_TOKEN environment variables.

```yaml
name: GitHub integration with TestOps

on:
  push:
    branches: [main]
  workflow_dispatch:

env:
  ALLURE_ENDPOINT: https://testops.example.com
  ALLURE_PROJECT_ID: 1
  ALLURE_RESULTS: build/allure-results

jobs:
  tests:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Install and configure allurectl
        uses: allure-framework/setup-allurectl@v1
        with:
          allure-endpoint: ${{ env.ALLURE_ENDPOINT }}
          allure-project-id: ${{ env.ALLURE_PROJECT_ID }}
          allure-token: ${{ secrets.ALLURE_TOKEN }}
      - name: Run tests
        run: allurectl watch -- ./gradlew clean test

```

--------------------------------

### Apply the Pipeline with kubectl

Source: https://docs.qameta.io/allure-testops/reference/integrations/ci-systems/tekton

Applies the 'allure-example-pipeline.yaml' file to create the Tekton Pipeline in the cluster.

```bash
kubectl apply -f allure-example-pipeline.yaml

```

--------------------------------

### allurectl watch --help

Source: https://docs.qameta.io/allure-testops/reference/ecosystem/allurectl

Displays help information for the watch command.

```bash
allurectl watch --help

```

--------------------------------

### AQL negative filter: not tag in ["nighlty", "devbuild"]

Source: https://docs.qameta.io/reference/aql

Use 'not' in an AQL query to get entities that do not have the specified tags. The example returns Allure TestOps entities that don't have tag 'nightly' or don't have tag 'devbuild'.

```aql
not tag in ["nighlty", "devbuild"]

```

--------------------------------

### Using the GitHub Action

Source: https://docs.qameta.io/allure-testops/reference/integrations/ci-systems/github

Complete example of a GitHub Actions workflow that runs tests and uploads results to Allure TestOps. It includes workflow_dispatch inputs for TESTS_BROWSER and service parameters.

```yaml
name: run-and-upload-to-testops

on:
  workflow_dispatch:
    inputs:
      TESTS_BROWSER:
        description: "Browser to be used in tests"
        required: true
        default: chrome
      ALLURE_JOB_RUN_ID:
        description: "Allure TestOps service parameter. Leave blank."
        required: false
      ALLURE_USERNAME:
        description: "Allure TestOps service parameter. Leave blank."
        required: false

env:
  ALLURE_RESULTS: allure-results
  ALLURE_JOB_RUN_ID: ${{ github.event.inputs.ALLURE_JOB_RUN_ID }}

```

--------------------------------

### Kubernetes SMTP configuration in values.yaml

Source: https://docs.qameta.io/allure-testops/server/configure/smtp

Edit these fields in values.yaml to configure SMTP for Kubernetes deployments. The example shows a typical authenticated SMTP setup with host, port, authentication, sender address, and TLS settings. Replace placeholders with your own mail host, account, and secret values.

```yaml
smtp:
  enabled: true
  host: smtp.example.com
  port: 587
  authEnabled: true
  from: noreply@example.com
  username: noreply@example.com
  password: <smtp-password>
  startTLSEnabled: true
  startTLSRequired: true
  sslEnabled: true
  sslTrust: smtp.example.com

```

--------------------------------

### Environment variables example for watch

Source: https://docs.qameta.io/allure-testops/reference/ecosystem/allurectl

Sets the required environment variables (ALLURE_ENDPOINT, ALLURE_TOKEN, ALLURE_PROJECT_ID, ALLURE_RESULTS, ALLURE_LAUNCH_NAME) and runs allurectl watch to execute tests and upload results.

```bash
# defined somewhere in the pipeline or on the CI project level
export ALLURE_ENDPOINT=https://testops.example.com
export ALLURE_TOKEN=55555555-5555-5555-5555-555555555555
export ALLURE_PROJECT_ID=100
export ALLURE_RESULTS=build/allure-results
export ALLURE_LAUNCH_NAME="Nightly API tests"

#  executing tests and uploading results
./allurectl watch -- ./gradlew clean test

```

--------------------------------

### Docker Compose SMTP configuration in .env

Source: https://docs.qameta.io/allure-testops/server/configure/smtp

Edit these variables in .env to configure SMTP for Docker Compose deployments. The example shows a typical authenticated SMTP setup with host, port, authentication, sender address, and TLS settings. Replace placeholders with your own mail host, account, and secret values.

```dotenv
SMTP_HOST=smtp.example.com
SMTP_PORT=587
SMTP_USERNAME=noreply@example.com
SMTP_PASSWORD=<smtp-password>
SMTP_MAIL_FROM=noreply@example.com
SMTP_AUTH=true
SMTP_STARTTLS_ENABLE=true
SMTP_STARTTLS_REQUIRED=true
SMTP_SSL_ENABLE=true
SMTP_SSL_TRUST=smtp.example.com

```

--------------------------------

### Add Qameta repository

Source: https://docs.qameta.io/allure-testops/server/install/linux-packages/deb

Adds the Qameta DEB repository to /etc/apt/sources.list.d/qameta.list. Must be pasted as a whole, without running its lines separately.

```bash
cat <<EOF | sudo tee /etc/apt/sources.list.d/qameta.list
deb [trusted=yes] https://dl.qameta.io/artifactory/deb-local stable main
EOF
```

--------------------------------

### Configure LDAP authentication

Source: https://docs.qameta.io/allure-testops/server/install/linux-packages/deb

Example LDAP configuration for Allure TestOps. Requires SMTP to be enabled. Adjust values according to your identity provider.

```bash
ALLURE_LOGIN_PRIMARY=ldap
ALLURE_LOGIN_LDAP_ENABLED='true'
ALLURE_LOGIN_LDAP_REFERRAL=follow
ALLURE_LOGIN_LDAP_URL=ldap://ldap.url.here:port
ALLURE_LOGIN_LDAP_USERSEARCHBASE="ou=People,dc=space"
ALLURE_LOGIN_LDAP_USERSEARCHFILTER="uid={0}"
```

--------------------------------

### Create database user, database, and grant privileges

Source: https://docs.qameta.io/allure-testops/server/install/database

SQL commands to create a PostgreSQL user, create the testops database, and grant all privileges on the database and public schema. Replace the example user, password, and database names with your own values.

```sql
-- create a new database user
CREATE USER testops with encrypted password 'PaSSw0rd';
-- create the database
CREATE DATABASE testops TEMPLATE template0 ENCODING 'utf8' LC_COLLATE = 'en_US.UTF-8' LC_CTYPE = 'en_US.UTF-8';
-- grant all privileges to the user testops on the testops database
GRANT ALL PRIVILEGES ON database testops to testops;
-- connect to the database `testops`
\c testops
-- grant all privileges on the public schema
GRANT ALL PRIVILEGES ON SCHEMA public TO testops;
\q
```

--------------------------------

### Set Allure TestOps instance URL parameters

Source: https://docs.qameta.io/allure-testops/server/install/docker-compose

Define the TESTOPS_INSTANCE_URL, TESTOPS_INSTANCE_PORT, and TESTOPS_PROTO parameters to specify the URL, port, and protocol for accessing Allure TestOps. The example assumes HTTP on port 80.

```bash
TESTOPS_INSTANCE_URL=testops.example.com
TESTOPS_INSTANCE_PORT=80
TESTOPS_PROTO=http

```

--------------------------------

### Run allurectl upload with configuration file and results path

Source: https://docs.qameta.io/allure-testops/reference/ecosystem/allurectl

Command to run allurectl upload, requiring the path to results to be provided via command line parameter.

```bash
allurectl upload --config ./ctl-conf.yaml /path/to/results
```

--------------------------------

### Navigate to values.yaml directory

Source: https://docs.qameta.io/allure-testops/server/install/kubernetes

Changes the current directory to the location containing your prepared values.yaml file before deploying.

```bash
cd ~/allure-testops

```

--------------------------------

### Add Qameta repository

Source: https://docs.qameta.io/allure-testops/server/install/linux-packages/rpm

Adds the Qameta repository to /etc/yum.repos.d/qameta.repo. Replace USERNAME and PASSWORD with credentials from the support team. Must be pasted as a whole, not line by line.

```bash
cat <<EOF | sudo tee /etc/yum.repos.d/qameta.repo
[Qameta]
name=Qameta
baseurl=https://dl.qameta.io/artifactory/rhel/
enabled=1
gpgcheck=0
username=USERNAME
password=PASSWORD
EOF
```

--------------------------------

### Submit the PipelineRun with kubectl

Source: https://docs.qameta.io/allure-testops/reference/integrations/ci-systems/tekton

Creates the PipelineRun from the 'allure-example-pipelinerun.yaml' file.

```bash
kubectl create -f allure-example-pipelinerun.yaml

```

--------------------------------

### Restart Docker Compose services

Source: https://docs.qameta.io/allure-testops/server/upgrade/notes/26-1-1

Execute this command after setting RELEASE_TO_DEPLOY=26.1.1 and TESTOPS_TASKEXECUTOR_COREPOOLSIZE=200 in the .env file to apply the upgrade.

```bash
docker compose down && docker compose up -d

```

--------------------------------

### Run allurectl watch with configuration file

Source: https://docs.qameta.io/allure-testops/reference/ecosystem/allurectl

Command to run allurectl watch, providing the path to the configuration file.

```bash
allurectl watch --config ./ctl-conf.yaml
```

--------------------------------

### Example ldapsearch command

Source: https://docs.qameta.io/allure-testops/server/configure/authentication/ldap

Example ldapsearch command to find a group with common name 'admins'.

```bash
ldapsearch -x -H "ldap://ldap.example.org:389" -b "dc=example,dc=org" -D "cn=admin,dc=example,dc=org" -w "password" "(cn=admins)"

```

--------------------------------

### Docker compose upgrade

Source: https://docs.qameta.io/server/upgrade/notes/26-1-1

Set RELEASE_TO_DEPLOY=26.1.1 and ensure TESTOPS_TASKEXECUTOR_COREPOOLSIZE is 200, then run these commands to upgrade.

```bash
docker compose down && docker compose up -d
```

--------------------------------

### Configure authentication with username and password

Source: https://docs.qameta.io/allure-testops/server/install/kubernetes

Set the primary authentication method to system with defaultRole ROLE_GUEST. ROLE_GUEST users do not consume licenses and have no project access, helping control license consumption.

```yaml
auth:
  primary: system
  defaultRole: ROLE_GUEST

```

--------------------------------

### Install TestOps plugin for Allure

Source: https://docs.qameta.io/allure-testops/howto/build-quality-gates

Installs the @allurereport/plugin-testops npm package, required to upload from allure run to TestOps.

```bash
npm add @allurereport/plugin-testops

```

--------------------------------

### Add Qameta Helm repository

Source: https://docs.qameta.io/allure-testops/server/install/kubernetes

Adds the Qameta Helm repository to your local Helm configuration. Run this before refreshing repository data.

```bash
helm repo add qameta https://dl.qameta.io/artifactory/helm

```

--------------------------------

### allurectl configuration file (ctl-conf.yaml)

Source: https://docs.qameta.io/allure-testops/reference/ecosystem/allurectl

Example allurectl configuration file. It shows how to avoid storing the API token in the file by using the ALLURE_TOKEN environment variable, and includes project-id, launch-name, launch-tags, exclude-files, skip-too-big, and ignore-passed-test-attachments settings.

```yaml
# avoid token in the file by all means
# use secret/environment variable ALLURE_TOKEN of your CI to pass token info
# token: avoid-using-your-api-token-here

project-id: 999
launch-name: "Static launch name"
launch-tags:
  - "regress"
  - "progress"
  - "egress"
# other parameters on the level 1

exclude-files:
  - "[0-9a-f-]+-container\.json"
skip-too-big: true
ignore-passed-test-attachments: false
```

--------------------------------

### Download allurectl for Linux x64

Source: https://docs.qameta.io/allure-testops/reference/ecosystem/allurectl

Downloads the latest allurectl binary for Linux amd64 and makes it executable.

```bash
wget https://github.com/allure-framework/allurectl/releases/latest/download/allurectl_linux_amd64 -O ./allurectl
chmod +x ./allurectl

```

--------------------------------

### Upgrade Allure TestOps box package with yum install

Source: https://docs.qameta.io/allure-testops/server/upgrade/archive/v4-rpm-installation

Installs the 'box' option of Allure TestOps. Replace 4.22.1 with the version you are upgrading to.

```bash
sudo yum install -y allure-testops-box-4.22.1

```

--------------------------------

### Upgrade Allure TestOps min package with yum install

Source: https://docs.qameta.io/allure-testops/server/upgrade/archive/v4-rpm-installation

Installs the 'min' option of Allure TestOps. Replace 4.22.1 with the version you are upgrading to.

```bash
sudo yum install -y allure-testops-min-4.22.1

```

--------------------------------

### Support ticket subject line

Source: https://docs.qameta.io/allure-testops/cloud/move-from-server-to-cloud

Use this exact subject line when creating a support ticket at help.qameta.io to initiate the migration. Replace <instance_name> with the Cloud instance domain and <your_company_name> with your company name.

```plaintext
Migration to SaaS <instance_name>.testops.cloud for <your_company_name>

```

--------------------------------

### LDAP Search Filter Example

Source: https://docs.qameta.io/server/configure/authentication/ldap

Example search filter that selects LDAP entries with objectClass person and uses the uid attribute as the user unique identifier.

```text
(&(objectClass=person)(uid={0}))

```

--------------------------------

### GitHub Actions workflow with setup-allurectl action

Source: https://docs.qameta.io/allure-testops/reference/integrations/ci-systems/github

Use this workflow to run pytest tests with Allure TestOps via the allure-framework/setup-allurectl action. It installs allure-pytest and pytest, configures allurectl with endpoint, token, and project ID, and runs tests with allurectl watch.

```yaml
jobs:
  all-tests:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v4
        with:
          python-version: "3.11"
      - name: Install test dependencies
        run: pip install allure-pytest pytest
      - name: Install and configure allurectl
        uses: allure-framework/setup-allurectl@v1
        with:
          allure-endpoint: https://testops.example.com
          allure-token: ${{ secrets.ALLURE_TOKEN }}
          allure-project-id: 1
      - name: Run tests
        run: allurectl watch -- pytest ./test --alluredir=${ALLURE_RESULTS}
        env:
          TESTS_BROWSER: ${{ github.event.inputs.TESTS_BROWSER }}

```

--------------------------------

### Login to Qameta Docker repository

Source: https://docs.qameta.io/allure-testops/server/install/docker-compose

Authenticate Docker with the Qameta repository using credentials provided by the Qameta sales team. Replace USERNAME and PASSWORD with your actual credentials.

```bash
docker login --username USERNAME --password PASSWORD
```

--------------------------------

### Check operating system version

Source: https://docs.qameta.io/allure-testops/server/install/linux-packages/rpm

Run this command to verify that the OS is CentOS 8 or newer, or RedHat Enterprise Linux 8 or newer.

```bash
source /etc/os-release; echo $PRETTY_NAME
```

--------------------------------

### MCP Configuration Command and Arguments

Source: https://docs.qameta.io/reference/ecosystem/mcp-server

Use this configuration in IntelliJ IDEA's AI Assistant to connect to an MCP server. Set the command to 'npx' and provide the arguments with the MCP remote URL and authorization header.

```text
npx
```

```text
mcp-remote https://your-instance-url/api/mcp --header "Authorization: api-token your-testops-api-token"
```

--------------------------------

### Search filter example (&(objectClass=person)(uid={0}))

Source: https://docs.qameta.io/allure-testops/server/configure/authentication/ldap

Example of a search filter used to select LDAP entries. Allure TestOps uses the user unique identifier (usually the uid attribute).

```text
(&(objectClass=person)(uid={0}))
```