There are two different methods of authenticating to Jira: our latest connector version 2.*.* uses Atlassian's OAuth 2.0 (3LO) method, while our version 1.*.* connector uses Atlassian's OAuth 1.0a method.
Follow Atlassian's instructions for enabling OAuth 2.0 for your account.
Navigate to your Transposit application. Add transposit/jira as a data connection.
Configure this data connection. Enter the client ID and secret for your OAuth2 app.
Authorize the configured data connection as usual.
Add an SQL operation from the Jira connector to your Transposit application. You'll note that there is an extra SQL clause:
-- The following parameters have been populated with suggested values
WHERE cloudid='(SELECT id FROM jira.get_cloudid)'
You'll need to remove the single quotes from around the SELECT clause to enable Transposit to query Jira for your cloudid value:
-- The following parameters have been populated with suggested values
WHERE cloudid=(SELECT id FROM jira.get_cloudid)
Note that jira.get_cloudid
is also a provided operation: you can use it as needed to obtain that value to save as an environment or stash variable for use in other operations.
That's it! You should now be able to query the Jira API using Transposit.
You will need to register your Transposit application as an OAuth consumer to connect it to Jira. After, you can authenticate with your Jira account and interact with the Jira API.
Follow Step 1. Configure Jira in Jira's OAuth documentation. This process includes a couple tasks:
Once you have successfully created an application link, keep your RSA private key available for the next step.
Navigate to your Transposit application. Add transposit/jira as a data connection.
Configure this data connection. You will need to specify a couple values specific to your Jira instance:
Auth URI | https://<instance>.atlassian.net/plugins/servlet/oauth/authorize |
Access Token URI | https://<instance>.atlassian.net/plugins/servlet/oauth/access-token |
Request Token URI | https://<instance>.atlassian.net/plugins/servlet/oauth/request-token |
Configure Authentication for this data connection. The Consumer Key should always be OauthKey. The Private Key should be a processed version of the RSA private key you generated previously. Specifically, remove the header and footer from the key, and then remove all line breaks from the body.
jira_privatekey.pcks8
-----BEGIN PRIVATE KEY----- <--- remove this
... <--- remove line breaks from this and copy it
-----END PRIVATE KEY----- <--- remove this
Save this configuration.
You should now be able to authenticate with your Jira account through Transposit.
Navigate to your Transposit application. Add a key for your Jira data connection. Allow your Transposit application to access your Jira data.
Delete the public and private keys you generated on your local machine. You no longer need them now that you've confirmed the integration is working.
That's it! You should now be able to query the Jira API using Transposit.