JIRA Application Configuration Details
You start the configuration in Step 2 in Part II. Install and Configure an AppSpokes Application. Most applications require additional configuration located on the second tab of the configuration page of the Application in AppSpoke's Universal Extension Manager (UEM).
For applications such as JIRA that supports integrations with multiple instances of the remote system, you will first select Add JIRA Instance to add the configuration detail of a JIRA instance.
Enter Name of your JIRA instance (it can be anything that identifies the instance to your users) and JIRA URL of the instance.You will obtain Client ID and Client Secret from OAuth Client in Atlassian JIRA. You will follow instructions in the sections below to create an OAuth client in JIRA.
Plugin Installation in Atlassian JIRA
To create an OAuth client in JIRA, you will first need to install the Social Business Enabler (SoBiE) add-on on your Atlassian JIRA server. A JIRA AppSpokes plugin is also required for the integration application to work.
Please check platform compatibility below to verify compatibility with your Atlassian product version.
Key: - Supported | - Unsupported | - Conditional | - Unknown
|JIRA 6||need further confirmation|
|JIRA 7||tested with 7.2.x|
|JIRA Data Center||need to update to use data center libraries|
To install SoBiE and JIRA AppSpokes plugins, follow the steps below:
- Download SoBiE obr file and JIRA Appspokes jar file from the Downloads page.
- Log into the Atlassian application with an administrator account.
- Browse to the Universal Plugin Manager (UPM).
- Click on the Upload add-on link.
- Select jira-appspokes-plugin-x,x.jar file and upload the add-on
- Repeat step 4 and 5 for sobie-x.x.obr file.
Create OAuth Client in Atlassian JIRA
To create a new OAuth 2 client, we need to use the Application Links feature from Atlassian products. The instructions below shows the steps for creating a client in JIRA, but can be applied to other Atlassian products such as Confluence, Bamboo, and Bitbucket.
- Log into the Atlassian JIRA with an administrator account.
- Browse to the Application Links administration page.
Enter the fully qualified URL of the integration application (https://jira.appspokes.net), and click the Create new link button.
- Verify the External URL and New URL are the same, and click the Continue button.
Fill in the Application Name and Application Type fields. Leave all other fields blank, and click the Continue button.
Application Name Name for this application link, e.g. AppSpokes JIRA. Application Type This has to be set to AppFusions Application.
You should see a new application link created and listed, along with a success message, as shown below.
Click on the edit icon of the newly created application link. Select the Incoming Authentication option in the application link configuration dialog, and fill in all the fields, and click the Save button.
Domain The domain used to validate incoming requests with. This should be the domain of the integration spoke application. Redirect URL The fully qualified URL to redirect users back to after authorization has been granted. This should be provided by the integration spoke application. Access token lifespan Specify how long the access token will be valid for. Note the shorter you set this, the more often a refresh will be required for access tokens. Default is 24 hours. Refresh token lifespan Specify how long the refresh token will be valid for. This should not be set too short, otherwise if a refresh token expires too soon, end users will be prompted to run through the authorization process again. Default is 720 hours (30 days).
- You should see a success message displayed, along with the auto-generated Client Id and Client Secret values.
Copy Client Id and Client Secret and paste them onto the JIRA application configuration page in AppSpokes UEM.
Note: If you are using FireFox, you are not able to copy data from disabled fields due to this known FireFox issue. We recommend you switch to a different browser such as Chrome, then return to the Incoming Authentication tab of this Application Link to copy the Client Id and Client Secret.
Jump back to IBM Connections
Integration Product Pages for: