I see login buttons in Jira when trying to use Allure TestOps plugin for Jira

Modified on Wed, 30 Jul at 12:48 PM

Authentication is a must

Some of the test cases, launches and test results could have the data which might be considered by your company as sensitive or even confidential and potentially can compromise some data that must not be disclosed.

So, there is no way to use Allure TestOps plug-in for Jira Software cloud without having an account in Allure TestOps and being authenticated in Allure TestOps.

You can create Guest accounts for the users that just need to see what is happening and do not need to perfrom any other actions.

These Guests need to be added to the projects they are interested in (correct authorisation is a must as well) and they'll see all the data from the Allure TestOps instance.

I see login buttons in Jira when trying to use Allure TestOps plugin for Jira

In 90% of cases, the authorization issue is resolved by following the instructions: The Allure sections display login buttons.However, if that didn't work for you, then check the following steps

Check if the Secure Cookie parameter is enabled
For integrations with Jira (DC/Cloud/Server), the Secure Cookie settings must be enabled in your instance configuration.

You can verify this by checking the relevant section in Dev Tools.

If the Secure field (4) is not checked, you need to review your instance settings and ensure that the parameter responsible for Secure Cookies is set to true.

K8s

Docker

If after following these steps the "Login" button is still displayed, the issue is likely with your Nginx configuration, which is blocking external authorization.

How to fix the external authorization error

To allow external authorization in Nginx, you need to add the following headers to the Nginx configuration

Access-Control-Allow-Headers: X-Custom-Header, Authorization

Explanation: These headers allow the client (e.g., a browser) to send specific data, such as authentication tokens or custom headers, to the server during cross-origin requests (CORS). Without these headers, the browser blocks the requests, which may cause authorization issues.

What you need to do:

Ensure that these headers are added to the Nginx configuration on your server.
Check that these settings are correctly configured, especially if you have a dedicated domain for external access to the system.