---
title: "How to avoid CAPTCHA when using Jira CLI"
canonical: "https://support.appfire.com/space/SUPPORT/89136699/How%20to%20avoid%20CAPTCHA%20when%20using%20Jira%20CLI"
format: markdown
---
## Problem Statement

> Macro (excerpt)
> 
> This article describes how to avoid *<span style="color: #172b4d">CAPTCHA </span>*<span style="color: #000000">when </span><span style="color: #000000">using a Jira CLI command and</span><span style="color: #000000"> the </span>*<span style="color: #000000">Maximum Authentication Attempts Allowed </span>*<span style="color: #000000">option</span><span style="color: #000000"> is set to 3 or less</span>.

### **Background**

When we set *<span style="color: #000000">Maximum Authentication Attempts Allowed to</span>*<span style="color: #000000"> 3 as shown in below screenshot, we are instructing Jira to allow the user to login for 3 times before the CAPTCHA is generated. </span>

![image](media://fea54d77-029a-4823-b033-d7291cc77021)

When the password is incorrectly provided in all the attempts, the user statistics show as follows:

![image](media://f700cfb8-cb0e-42c9-ad98-d97c36eb5771)

## Environment

| **Application** | JIRA |
| --- | --- |
| **Version** | Server |
| **App Version** | Below 8.6.0 |

## Error Message

<span style="color: #000000">The following log message is displayed on the console:</span>

```plaintext
Remote error: User 'test' is not allowed to log in at this point in time perhaps due to CAPTCHA requirements.
```

  
In the case of Jira CLI, it retries the login attempt thrice by default. When the password is incorrectly provided, these three attempts by CLI are considered as the maximum authentication attempts allowed, leading to a CAPTCHA.

## Solution

 The solution lies in having the Jira CLI to try the login only once in the background. To do this perform the following:

1. Upgrade to **8.6.0 or **the latest **version** of CLI from this [link](https://appfire.atlassian.net/wiki/spaces/ACLI/pages/60562669) in case you are using a lower version.
2. Use the option **--options noCommRetry** on the action to avoid the retry attempts from Jira CLI. This option allows CLI to check for the authentication only once.

```shell
--action createIssue --project TEST --options noCommRetry
```

> ℹ️ It is always recommended to use the latest ACLI [Release notes](https://appfire.atlassian.net/wiki/spaces/ACLI/pages/60563196).