Atlassian Jira Service Desk

introduction this guide tells you how to authenticate the atlassian jira service desk connector in swimlane the connector supports two authentication methods http basic authentication (username and api token) – recommended for atlassian cloud http bearer authentication (bearer token) – for environments using oauth 2 0 bearer access tokens you will generate an api token (or obtain a bearer access token), collect the required credentials, and configure the connector in swimlane prerequisites atlassian access requirements you must have permissions to access your jira service management (jira service desk) instance generate atlassian api tokens (for basic authentication), or create and use oauth 2 0 applications (for bearer authentication) access the jira service desk rest apis required credentials for http basic authentication during setup, you will collect jira service desk url username (atlassian account email) api token for http bearer authentication during setup, you will collect jira service desk url bearer access token atlassian setup http basic authentication take the following steps to generate an api token sign in to your atlassian account navigate to account settings select security under api tokens , click create api token enter a label for the token click create copy and securely save the generated api token this token is displayed only once take the following steps to collect the jira service desk url log in to jira service management copy your jira instance url from the browser example https //company atlassian net use this value as the url during connector configuration connector configuration in swimlane http basic authentication 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 service desk from the asset type list select jira service desk http basic authentication fill in the asset settings and asset input as shown field description required/optional url jira service desk instance url required username atlassian account email required password atlassian api token required verify ssl enable/disable ssl verification optional http proxy optional proxy configuration optional fields with marks are required click create http bearer authentication (oauth 2 0) take the following steps to obtain a bearer access token create an oauth 2 0 application in the atlassian developer console configure the required oauth scopes for jira service management complete the oauth 2 0 authorization flow exchange the authorization code for an access token copy and securely save the bearer access token refer to the atlassian oauth 2 0 documentation for detailed application registration and authorisation steps after obtaining the bearer token, take the following steps 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 service desk from the asset type list select jira service desk http bearer authentication fill in the asset settings and asset input as shown field description required/optional url jira service desk instance url required token oauth 2 0 bearer access token required verify ssl enable/disable ssl verification optional http proxy optional proxy configuration optional fields with marks are required click create troubleshooting authentication failed (401 unauthorized) verify that the api token or bearer token is valid the username is your atlassian account email (for basic authentication) the token has not expired or been revoked permission denied (403 forbidden) verify that your account has permission to access jira service management apis the oauth application has the required scopes your user account has permission to access the requested service desk unable to connect verify that the jira service desk url is correct your jira cloud instance is reachable firewall or proxy settings allow https traffic ssl errors if ssl verification fails verify that the jira instance uses a trusted ssl certificate confirm that any proxy is not intercepting ssl traffic disable verify ssl only for testing if permitted by your organization's security policy result you have successfully authenticated the atlassian jira service desk connector in swimlane sources atlassian api token management https //support atlassian com/atlassian account/docs/manage api tokens for your atlassian account/ https //support atlassian com/atlassian account/docs/manage api tokens for your atlassian account/ atlassian oauth 2 0 (3lo) documentation https //developer atlassian com/cloud/jira/platform/oauth 2 3lo apps/ https //developer atlassian com/cloud/jira/platform/oauth 2 3lo apps/ atlassian jira service management rest api documentation https //developer atlassian com/cloud/jira/service desk/rest/ https //developer atlassian com/cloud/jira/service desk/rest/