Steps to replicate

• Create a new job of any type, and enter a credential with a correct username and incorrect password
• Attempt a few operations where Jenkins will use that password, e.g. type a few letters at a time into the project name field
• Verify the failed authentication attempts have triggered a CAPTCHA challenge by trying to login with the created username in Bitbucket
• Correct the credential, and try to create the job as normal

Expected behaviour
At the very minimum, the error should indicate the credential is not working because of CAPTCHA and this should be resolved for the credential to be usable.

Actual behaviour
Error message provided is the more ambiguous "provided credential cannot access resource"- technically correct, but easy to confuse with the credential itself being wrong.

Workaround
No workaround- this is a UI issue. The credential will work again if the CAPTCHA is resolved in Bitbucket.