You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 5
Next »
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)
- password (access token)
| - Atlassian has removed support for use of Basic and Session authentication
- UPM client also supports the same authentication methods
|
| Jira Server | Parameters | 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 | 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 |
|
| - UPM client also supports the same authentication methods
|
| Bitbucket Server | Parameters |
| Personal Access Tokens Parameters 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 |
| App passwords- user (user name)
- password (app password)
| |
| Trello |
|
| Trello Token Parameters |
|
| Slack | Parameters |
|
| |
