Overview

There are various authentication options used by Atlassian applications for remote access. The following are those available and supported by the CLI at least on the latest release levels.

Application	Basic Authentication	Session Authentication	OAuth and Related Tokens	Discussion
Jira, Confluence Cloud	No longer available	No longer available	Atlassian Personal Access Tokens (also known as API Tokens) Parameters user (email address) token or password (access token)	Atlassian has removed support for use of Basic and Session authentication Deprecation notice - Jira - JCLI-1468 Deprecation notice - Confluence - CSOAP-990 UPM client also supports the same authentication methods CLI 8.4 or higher can use the token parameter for their access token instead of password parameter - either works the same (except for a couple of cases where a real password is needed) If you are NOT using the email address and API token for your user credentials for accessing Cloud sites, you will likely receive: Remote error: User is not authorized to perform the request. Response code: 401.
Jira Server	Parameters user (user name) password	Parameters user (for login) password (for login) login (subsequent actions) Default with automatic login	JCLI-1220	Let default support use automatic session authentication Only special case, advanced scripting should bother with using login action and saved sessions UPM client also supports the same authentication methods
Confluence Server	Parameters user (user name) password	Parameters user (for login) password (for login) login (subsequent actions) Default with automatic login		Let default support use automatic session authentication Only special case, advanced scripting should bother with using login action and saved sessions UPM client also supports the same authentication methods
Bamboo Server	Parameters user (user name) password			UPM client also supports the same authentication methods
Bitbucket Server	Parameters user (user name) password		Personal Access Tokens Parameters token Supported Bitbucket Server 5.5 and higher CLI 7.8 and higher	UPM client also supports the same authentication methods See also Access Tokens.
Bitbucket Cloud	Parameters user (user name) password		App passwords user (user name) password (app password)	See also Access Tokens for Bitbucket.
Trello			Trello Token Parameters token
Slack	Parameters token			See Access Tokens for Slack.
Tempo Cloud			Parameters tempoToken	See How to create a Tempo Cloud API token.

Authentication

Overview