When integrating Testlab with your Atlassian products such as JIRA, there might be credentials related to your Atlassian side. Previously, for example with JIRA, the integrations required you to create a user account to JIRA and configure the credentials (including the password) to your Testlab project. Atlassian has made some changes and at least with JIRA Cloud, using passwords in this kind of scenario has been deprecated.
Documentation for setting up our integrations have been updated. In this post, we also provide instructions on what to do to get your integrations up and running.
Replacing passwords with API tokens
At least for some operations, the integrations rely on operations provided by JIRA’s so-called REST APIs. It might vary a bit depending on your JIRA version, but at least with the current JIRA Cloud, you should replace all passwords with so-called API tokens. What you should do is that for the (JIRA) user you are integrating with, you should create an API token and use the token as the password at the Testlab side. For technical details, you can read more about JIRA’s authentication via the links provided at the end of this article.
When using JIRA Cloud, to create an API token,
- With the user account you are integrating with, log in to https://id.atlassian.com/manage/api-tokens
- Click Create an API token
- Give your token a label and click Create
- Click Copy to clipboard and paste the token as a “password” when configuring the integration at Testlab side
That’s it. Your server installed JIRA might also require the use of API tokens. If so, refer to your JIRA administrator or JIRA documentation on help on how to do this.