I don't see why it would be a security hole for me as an administrator to designate one account to have captchas disabled. I am attempting to get authentication working for a service account to use the API, and having captchas turned on everytime my login attempts fail a few times is a pain because it means that any future attempts will definitely fail until I clear it.
We have same issue on our integration with JIRA using API - from time to time we get capcha validation for service account used for the integration altrough we always use valid user name and password.
Any solution for that?
I would see a possibility to add list of exception in JIRA where admins could add all system accounts to disable cptcha at all for them.
I'm also looking at the possibility of disable for just some specific accounts.
For some weird reason, my API calls are getting 403 / 401s despite the fact that I'm using correct credentials. The issue is actually very intermittent. A total failure happens when the CAPTCHA is triggered. Someone has to go to the admin page and reset login count.
It's a huge problem for us right now and I see that some are getting the same authentication failure issue.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events