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 // http //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 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 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> http //atlassian net/ validate ssl settings you have successfully authenticated the atlassian jira connector in swimlane