---
title: Atlassian Jira On-Premise
slug: authentication-guides/atlassian-jira-on-premise
docTags: 
createdAt: 2026-01-19T21:44:37.099Z
---

# 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:

1. Log in to the Jira On-Premise web interface.
2. Navigate to your user profile.
3. Open the Personal Access Tokens section.
4. Click Create token.
5. Enter a label and expiration.
6. 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:

1. Generate a Personal Access Token as described above.
2. Use the token as a Bearer token in Swimlane configuration.

# Connector Configuration in Swimlane

Take the following steps to configure the connector:

1. Log in to Turbine.
2. From the left-hand navigation pane, click **ORCHESTRATION** and click **Assets**.
   Asset homepage opens.
3. Click the **plus** icon to open the Configure your Connector Asset window.
4. Select **Atlassian JIRA On-Premise** from the Asset type list.
5. 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           |

![](https://api.archbee.com/api/optimize/n8uUzk0MM4uC57-zlHNtY/f4otvrYpbERCrOZ4PfdCJ_image.png)

## 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           |

![](https://api.archbee.com/api/optimize/n8uUzk0MM4uC57-zlHNtY/ZVxj8tUbE9qlzN9zsurCi_image.png)

# 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.