Jira authentication guide

This is a step-by-step guide to acquiring Jira credentials to authorize the Jira Load and Jira Query components.

These components use either a username and password or a username and API token for third-party authentication. This guide will only explain the username and API token method.

Authorizing the Jira Load or Jira Query component includes four steps:

1. Obtain an API token from the Atlassian portal.
2. Create a secret to store the Atlassian API Token.
3. Add a secret definition to the Your projects menu.
4. Use the API Token property drop-down in the component properties to select the Jira token you have created.

---

Obtain an API token

1. Log in to the API tokens section of the Atlassian portal.
2. Follow the instructions in the Atlassian Create an API token documentation to create a new API token.

Note

• Make sure to copy the API token immediately as it will only appear once.
• When copying the token, some browsers may add a space to the end of the string. Watch out for this as it will cause the credentials to fail.

You can now exit the Atlassian portal and return to the Data Productivity Cloud.

---

Create a secret

You must create a secret to store your Atlassian API Token. How this secret is stored depends on your Data Productivity Cloud deployment model:

• In a Full SaaS deployment model, you must add a secret to the internal managed vault service that is hosted in Matillion's own AWS infrastructure. Read Secrets and secret definitions for details.
• In a Hybrid SaaS deployment model, you must add a secret to either AWS Secrets Manager or Azure Key Vault in your own cloud infrastructure, as described below.
• In a Hybrid SaaS deployment model using Matillion Agent for Snowflake, read Secrets in Matillion Agent for Snowflake for details of how to store the secret in a Snowflake schema.

AWS Secrets Manager

1. Log in to the AWS account that houses your agent. This must be in the same AWS Region as the agent selected when the project was created.
2. In the search bar search for Secrets Manager to access the Secrets page.
3. Click Store a new secret.
4. Select Other type of secret and create a Key/value pair with the following details:
   • Key: Enter a label you will use to identify the token.
   • Value: Enter the Atlassian API Token code you copied earlier.
5. Click Next and on the next page enter a Secret name. This is the name that will appear in the Secret definitions list in Your projects.
6. The remainder of the details aren't needed, so click Next and Next again, then Store to complete the creation of the secret.

Azure Key Vault

1. Log in to the Azure account that houses your agent. This must be in the same Azure Region as the agent selected when the project was created.
2. Click Key vaults and click the name of the key vault you want to reference. If there is only one, then this will be the [Default] key vault configured in the agent.
3. Click Objects and then click Secrets.
4. Click + Generate/Import.
5. On the Create a secret screen enter the following:
   • Upload options: Select Manual.
   • Name: Type a name for the secret. The secret name must be unique within a key vault. For more information on naming, read Key Vault objects, identifiers, and versioning.
   • Secret value: Enter the Atlassian API Token code you copied earlier.
6. Click Create.

---

Add a secret definition

Follow the steps in Secrets and secret definitions.

---

Return to Designer

1. Return to the component properties in Designer.
2. Click into the API Token property.
3. Select your new secret definition representing your Jira API token.
4. Click Save.

Got feedback or spotted something we can improve?

We'd love to hear from you. Join the conversation in the Documentation forum!