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