Configuring Captcha for Failed Logins
If you have confluence administrator permissions, you can configure Confluence to impose a maximum number of repeated login attempts. After a given number of failed login attempts (the default is three) Confluence will display a Captcha form asking the user to enter a given word when attempting to log in again. This will prevent brute force attacks on the Confluence login screen.
Similarly, after three failed login attempts via the XML-RPC or SOAP API, an error message will be returned instructing the user to log in via the web interface. Captcha will automatically be activated when they attempt this login.
On this page:
'Captcha' is a test that can distinguish a human being from an automated agent such as a web spider or robot. When Captcha is activated, users will need to recognise a distorted picture of a word, and must type the word into a text field. This is easy for humans to do, but very difficult for computers.
Screenshot: example of a Captcha test
/download/attachments/216957808/captcha.png?version=1&modificationDate=1272411042125&api=v2" width="784" align="center"/>
Enabling, Disabling and Configuring Captcha for Failed Logins
By default, Captcha for failed logins is enabled and the number of failed login attempts is set to three.
To enable, disable and configure Captcha for failed logins:
- Choose the cog icon , then choose General Configuration under Confluence Administration
- Choose 'Security Configuration' from the left menu.
- Choose 'Edit'.
- To enable Captcha:
- Select the 'Enable' checkbox next to 'CAPTCHA on login'.
- Set the maximum number of failed logins next to 'Maximum Authentication Attempts Allowed'. You must enter a number greater than zero.
- To disable Captcha, deselect the 'Enable' checkbox.
- Choose 'Save'.
Screenshot: Configuring Captcha for failed logins
- Disabling all password confirmation requests, including Captcha on login. Confluence installations that use a custom authentication mechanism may run into problems with the Confluence security measure that requires password confirmation. If necessary, you can set the
password.confirmation.disabledsystem property to disable the password confirmation functionality on administrative actions, change of email address and Captcha for failed logins. See Recognised System Properties.
Was this helpful?
Thanks for your feedback!