Atlassian Jira On-Premise
Introduction
This guide explains how to authenticate the Atlassian Jira On-Premise connector in Swimlane using the supported authentication methods.
You will generate Jira credentials, collect the required instance details, and configure the connector inside Swimlane Turbine.
Authentication Methods Overview
The Atlassian Jira On-Premise connector supports the following authentication methods:
- HTTP Basic Authentication (Username + Password or Personal Access Token)
- HTTP Bearer Authentication (Personal Access Token)
Prerequisites
Jira Access Requirements
You must have Jira permissions to:
- Access your Jira On-Premise instance
- Generate or use a Personal Access Token (if enabled)
- Access Jira REST APIs
Required Credentials
During setup, you will collect:
- Jira Base URL
- Username
- Password or Personal Access Token
Jira Setup
Method 1 β HTTP Basic Authentication
This method authenticates using a Jira username and either a password or a Personal Access Token. Using a Personal Access Token is recommended.
Take the following steps to generate a Personal Access Token:
- Log in to the Jira On-Premise web interface.
- Navigate to your user profile.
- Open the Personal Access Tokens section.
- Click Create token.
- Enter a label and expiration.
- Copy and securely store the token.
Method 2 β HTTP Bearer Authentication
This method uses a Personal Access Token passed as a Bearer token in the Authorization header.
Take the following steps to use Bearer authentication:
- Generate a Personal Access Token as described above.
- Use the token as a Bearer token in Swimlane configuration.
Connector Configuration in Swimlane
Take the following steps to configure the connector:
- Log in to Turbine.
- 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 On-Premise from the Asset type list.
- Fill in the Asset Settings and Asset Input as shown:
Configuration β HTTP Basic Authentication
Field | Description | Required |
|---|---|---|
url | Jira Base URL | Yes |
username | Jira username | Yes |
password | Password or Personal Access Token | Yes |
verify_ssl | Verify SSL certificate | No |
http_proxy | Proxy configuration | No |
Configuration β HTTP Bearer Authentication
Field | Description | Required |
|---|---|---|
url | Jira Base URL | Yes |
token | Personal Access Token | Yes |
verify_ssl | Verify SSL certificate | No |
http_proxy | Proxy configuration | No |
Troubleshooting
401 Unauthorized
- Invalid username or token
- Expired or revoked Personal Access Token
403 Forbidden
- User lacks Jira permissions
- API access disabled
SSL Errors
- Verify SSL certificate configuration
- Adjust verify_ssl if required
You have successfully authenticated the Atlassian Jira On-Premise connector in Swimlane.