Unable to log into the QMetry Exploratory testing extension

Symptoms: When the user tries to login into QMetry’s exploratory testing extension, they observe an error - “You are not authorized to access QMetry Exploratory Testing with QMetry Test Management for Jira, please try again” as shown in the below screenshot:

Open

Below are the various scenarios where the user may observe this issue. Follow the mentioned solutions for respective scenario

• Scenario 1: The user does not have access to the Jira instance.

  • Solution: Verify if the user has access to the Jira instance. If not, the Jira admin needs to add the user to the instance.

• Scenario 2:The user is not part of “jira-software-users” group for the Jira instance they are trying ET recording.

  • Solution: The Jira admin needs to add the affected user to the “jira-software-users” group for the Jira instance.

• Scenario 3:The user is an inactive user (deactivated account).

  • Solution: For this scenario, the admin needs to restore the Jira access for the affected user’s account as only active users can use the ET extension.

• Scenario 4: If the user fulfills all of the above scenarios and still observes the error, then the following could be the root cause:
  The user directly logs in to the QMetry’s exploratory testing extension without logging into the same Jira instance.

  • Solution: Follow the steps mentioned below to resolve this issue:
    Note: The steps are to be followed by the affected user and not by the admin of the instance.

  • Step 1: On the same browser, log out from your Jira instance and re-log with the same URL, username, and password for Jira that you are trying to login into Exploratory Testing extension.

  • Step 2: Once you have successfully logged into Jira, log in to the exploratory extension using the same Jira base URL, and login id used in Step 1, and generate the API key by referring to the help guide link -Generate the API key.
    Add the API key generated by the affected user and click on the “Login” button.

In case the issue still persists, share the below logs with us:

• Console Logs for the exploratory extension.

• HAR Logs for the exploratory extension.