Skip to end of banner
Go to start of banner

Authentication

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 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.

ApplicationBasic AuthenticationSession AuthenticationOAuth and Related TokensDiscussion
Jira, Confluence Cloud 

Parameters

  • user (user name or email)
  • password

NOT available Dec 2018 for Jira

NOT available Jan 2019 for Confluence 

Parameters

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

Default with automatic login

NOT available Dec 2018 for Jira

NOT available Jan 2019 for Confluence

Atlassian Personal Access Tokens

(also known as API Tokens)

Parameters

  • user (email address)
  • password (access token)
  • Recommend: Use an access token now! It can be used as a replacement for your password 
  • Atlassian has deprecated use of Basic and Session authentication and is likely to remove support later in 2018
  • UPM client also supports the same authentication methods
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)
Hipchat Server and Cloud

Hipchat Access Tokens

Parameters

  • token

Trello

Trello Token

Parameters

  • token

Slack

Parameters

  • token


  • No labels