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.

Parameters

• user (user name)
• password

Parameters

• user (for login)
• password (for login)
• login (subsequent actions)

Default with automatic login

Using Personal Access Tokens

Requires 8.14 or higher.

Parameters

• token

• 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

Personal Access Token Restrictions

• See Restrictions section below for general information

Parameters

• user (user name)
• password

Parameters

• user (for login)
• password (for login)
• login (subsequent actions)

Default with automatic login

Using Personal Access Tokens

Requires 7.9 or higher.

Parameters

• token

• 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

Personal Access Token Restrictions

• See Restrictions section below for general information
• Cannot be used for user actions (getUserList, addUser, removeUser, editUser, ...) when admin security (websudo) is enabled.

Parameters

• user (user name)
• password

Bamboo Personal Access Tokens

Requires 6.10 or higher.

Parameters

• token

• UPM client also supports the same authentication methods

Personal Access Token Restrictions

• See Restrictions section below for general information

Parameters

• user (user name)
• password

Personal Access Tokens

Parameters

• token

• UPM client also supports the same authentication methods
• See also Access Tokens.

Personal Access Token Restrictions

• See Restrictions section below for general information

No longer available

• user (user name)
• password (app password)

Access tokens (11.0 and higher) parameters

• token 

• Bitbucket app passwords can be generated by going to your account settings and look for app passwords 

Bitbucket resource scoped access tokens - see Access Tokens for Bitbucket Cloud. These tokens have restricted capabilities, so should only be used for actions that can be achieved with the bounds of the specific restrictions otherwise the action will fail likely with an error like this. Remote error: This API is not accessible by this authentication mechanism . This is especially true for repository and project access tokens. Where appropriate, access tokens are recommended for automations - they are easily  managed by resource admins and have independent 429 limits. 

Trello Token

Parameters

• token

• See also Access Tokens for Trello

Parameters

• token

• See Access Tokens for Slack.

Parameters

• tempoToken

• See How to create a Tempo Cloud API token