---
title: "Authentication options"
canonical: "https://support.appfire.com/space/ACLI/60563795/Authentication%20options"
format: markdown
---
> Macro (aura-html)

# Overview

Atlassian applications offer several authentication options for API access. Below are the ones currently supported by the Command Line Interface (CLI) in the latest releases.

| App | Basic Authentication | Session Authentication | OAuth and Related Tokens | Discussion |
| --- | --- | --- | --- | --- |
| Jira, Confluence Cloud | No longer available | No longer available | [Atlassian Personal Access Tokens](https://confluence.atlassian.com/cloud/api-tokens-938839638.html)<br>(also known as API Tokens)<br>Parameters<br>- user (email address)
- token or password (access token) | - Atlassian has removed support for the use of Basic and Session authentication
  - [Deprecation notice](https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-basic-auth-and-cookie-based-auth/) - Jira
  - [Deprecation notice](https://developer.atlassian.com/cloud/confluence/deprecation-notice-basic-auth/) - Confluence
- UPM client also supports the same authentication methods
- CLI 8.4 or higher can use the **token** parameter for their access token instead of the **password** parameter - either works the same (except for a couple of cases where a real password is needed)
- <span style="color: #172b4d">If you are </span><span style="color: #172b4d">**NOT**</span><span style="color: #172b4d"> using the</span> email address and API token<span style="color: #172b4d"> for your user credentials for accessing Cloud sites, you will likely receive: </span><span style="color: #172b4d">**Remote error: User is not authorized to perform the request. **</span><span style="color: #172b4d">**Response code: 401**</span><span style="color: #172b4d">**.**</span> |
| Jira Server | Parameters<br>- user (user name)
- password | Parameters<br>- user (for login)
- password (for login)
- login (subsequent actions)<br>Default with automatic login | [Using Personal Access Tokens](https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html)<br>Requires 8.14 or higher.<br>Parameters<br>- token | - Let the default support use automatic session authentication
- Only in special cases, advanced scripting should be used with using *login* action and saved sessions
- UPM client also supports the same authentication methods<br>##### Personal Access Token Restrictions<br>- See the **Restrictions** section below for general information |
| Confluence Server | Parameters<br>- user (user name)
- password | Parameters<br>- user (for login)
- password (for login)
- login (subsequent actions)<br>Default with automatic login | [Using Personal Access Tokens](https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html)<br>Requires 7.9 or higher.<br>Parameters<br>- token | - Let default support use automatic session authentication
- Only in special cases, advanced scripting should be used with using *login* action and saved sessions
- UPM client also supports the same authentication methods<br>##### Personal Access Token Restrictions<br>- See the **Restrictions** section below for general information
- Cannot be used for user actions (getUserList, addUser, removeUser, editUser, ...) when admin security (websudo) is enabled. |
| Bitbucket Server | Parameters<br>- user (user name)
- password |  | [Personal Access Tokens](https://confluence.atlassian.com/bitbucketserver/personal-access-tokens-939515499.html)<br>Parameters<br>- token | - UPM client also supports the same authentication methods
- See also [Access Tokens](https://appfire.atlassian.net/wiki/spaces/SCLI/pages/73368178).<br>##### Personal Access Token Restrictions<br>- See the **Restrictions** section below for general information |
| Bitbucket Cloud | No longer available |  | App passwords parameters<br>- user (user name)
- password (app password)<br>Access tokens ([11.0](https://appfire.atlassian.net/wiki/spaces/ACLI/pages/168329518) and higher) parameters<br>- token | - Bitbucket app passwords can be generated by going to your [account settings](https://bitbucket.org/account/settings/) and looking for [app passwords](https://bitbucket.org/account/settings/app-passwords/).<br>Bitbucket resource-scoped access tokens - see [Access Tokens](https://support.atlassian.com/bitbucket-cloud/docs/access-tokens/) for Bitbucket Cloud. These tokens have restricted capabilities, so they should only be used for actions that can be achieved within the bounds of the specific restrictions; otherwise, the action will fail 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. |
| Slack | Parameters<br>- token |  |  | - See [Access Tokens](https://appfire.atlassian.net/wiki/spaces/SLACKCLI/pages/74023387) for Slack. |

# Personal Access Tokens for Server and Data Center

Personal access tokens have some good advantages in specific cases, but there are also some severe restrictions:

Personal access tokens can be created in the UI by going to your profile - see [Atlassian documentation on personal access tokens](https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html).

## Restrictions

1. Some server remote capabilities used in various CLI actions can not support access using personal access tokens - actions like `renderRequest` or actions that use similar support under the covers, depending on the action parameters used. In this case, you receive an error message such as:
  `Client error: Action or capability not available when using token authentication. Use user and password parameters instead.`  
Sometimes, you can avoid restricted capabilities by adjusting the parameters you use on the action. Otherwise, you need to revert to the standard user and password support.
2. If secure administrator sessions (websudo) are turned on for your instance and you attempt a secure administration action, websudo permission errors occur. Turn off the websudo for your site or revert to the standard user and password support.