Disable user CAPTCHAs from the JIRA database
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Steps
Always back up your data before making any database modifications. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.
Shutdown your JIRA application.
Execute the following SQL to identify the record to update:
1 2 3 4 5SELECT s.* FROM propertyentry e JOIN propertystring s ON e.id = s.id WHERE property_key = 'jira.maximum.authentication.attempts.allowed';And run the following SQL to set that record to an empty string, which is the equivalent of unlimited authentication attempts, bypassing CAPTCHA validation:
1 2 3UPDATE propertystring SET propertyvalue = '' WHERE id = <id from step 2>;Start JIRA application.
Additionally our How to reset failed login count from a JIRA application database KB may be of assistance.
This approach will disable CAPTCHA for all Jira users. To disable CAPTCHA for specific users, we have raised the following feature request ticket: JRASERVER-40362 Allow administrators to disable CAPTCHA for specific users
⚠️ Currently, CAPTCHA can not be disabled on Oracle databases. There is an open JAC ticket that can be voted on and watched for more information:
JRASERVER-41240 Unable to set Maximum Authentication Attempts Allowed to Unlimited on Oracle DB
Was this helpful?