Atlassian Jira

Introduction

This guide explains how to authenticate the Atlassian Jira connector in Swimlane using one of the supported methods:

HTTP Basic Authentication (username + API token)

HTTP Bearer Token Authentication (OAuth access token)

Custom Authentication (Access Token, Client Credentials, or Refresh Token)

You will generate Jira API credentials, collect required instance information, and configure the connector inside Swimlane Turbine.

Jira Access Requirements

You must have jira permissions to

Access your Atlassian account profile

Generate a Jira API token

View your Jira Cloud base URL

(For OAuth) Access the registered OAuth client details

(For Client Credentials) Work with your Atlassian admin to configure OAuth 2.0

Required Credentials

During setup, you will collect:

HTTP Basic Authentication

Jira Base URL

Jira Email Username

API Token

HTTP Bearer Token Authentication

Jira Base URL

OAuth Access Token

SSL Verification

Proxy

Custom Authentication

Jira Base URL

OAuth Client ID

OAuth Client Secret

Jira Setup

Method 1- HTTP Basic Authentication

Locate Jira base URL. Your Jira Cloud domain typically looks like: https://your-domain.atlassian.net

Go to: https://id.atlassian.com/manage-profile/security/api-tokens

Click Create API Token.

Enter a label (e.g., Swimlane).

Click Create.

Copy the generated token.

Make sure to copy and save the token value as it will not be shown again.

Method 2 - HTTP Bearer Token Authentication (OAuth Access Token)

This method is used when Jira is integrated via OAuth 2.0. You will obtain Access Token to authenticate. Your Atlassian admin or Identity Provider will provide either:

Access Token (directly). OR

Instructions to generate one using OAuth.

For Swimlane deployments, the Swimlane team will provide a Python script and instructions on how to use the script to generate the Access Token and Refresh Token using Oauth2.0.

Method 3 - Custom Authentication (Access Token / Client Credentials / Refresh Token)

This method supports advanced OAuth setups.

Confirm OAuth App registration. Your admin must provide:

OAuth Client ID

OAuth Client Secret

JIRA Base URI

Refresh Token (if applicable)

Access Token (if applicable)

SSL Verification (if applicable)

Proxy configuration (if applicable)

Connector Configuration in Swimlane

From the left-hand navigation pane, click ORCHESTRATION and click Assets. Asset homepage opens.

Click the plus icon to open the Configure your Connector Asset window.

Select Atlassian Jira from the Asset type list.

Choose the authentication method type.

Fill in the Asset Settings and Asset Input as shown:

Custom Authentication

Field	Description	Required
url	Jira Base URL	Required
access_token	Access Token	Optional
client_id	OAuth Client ID	Required
client_secret	OAuth Client Secret	Required
refresh_token	Refresh Token	Optional
verify_ssl	SSL Verification	Optional
http_proxy	Proxy configuration	Optional

HTTP Basic Authentication

Field	Description	Required
url	Jira Base URL	Required
username	Jira Email Username	Required
password	API Token	Required
verify_ssl	SSL Verification	Optional
http_proxy	Proxy	Optional

HTTP Bearer Authentication

Field	Description	Required
url	Jira Base URL	Required
token	OAuth Access Token	Required
verify_ssl	SSL Verification	Required
http_proxy	Proxy	Required

Click Create.

Troubleshooting

401 Unauthorized

Wrong token

Using expired access token

API Token deleted

Using wrong Jira username (must be Atlassian account email)

403 Forbidden

User or OAuth app lacks necessary Jira permissions

Missing scopes for Issue or Project APIs

Connection or SSL Errors

Ensure you are using https://<domain>.atlassian.net

Validate SSL settings

You have successfully authenticated the Atlassian Jira Connector in Swimlane.