OpenLDAP accounts don't lock after failed JIRA login attempts

Hi, I have set up a delegated LDAP authentication directory and I am now able to authenticate to JIRA using LDAP credentials.  I am (unsuccessfully) trying to get it so that OpenLDAP accounts lock after a certain number of failed JIRA login attempts.


I have configured ppolicy on the LDAP side, and the lockout mechanism works correctly if I try to login incorrectly to one of our other systems that are integrated with LDAP (OS authentication and subversion authentication).  On the LDAP side I get a new "pwdFailureTime" operational attribute for each failed login attempt, and then on the 5th failed attempt I get a "pwdAccountLockedTime" attribute.


But with JIRA I only get more and more "pwdFailureTime" attributes with each failed login attempt and the "pwdAccountLockedTime" attribute never appears.


Can anyone help?  Thanks very much.



2 answers

1 accepted

0 votes
Accepted answer


Could it be that pwdAccountLockedTime is not triggered due to Captcha?

There is also plugins enabling more advanced behaviour if you run out of options.

Thanks very much, your suggestion led me down the right path!  It was in a way related to the captchas.  The failed login attempts were getting expired in LDAP after 30 seconds.  So I didn't realize it, but I had to have 5 failed login attempts within the span of 30 seconds in order to lock the account, and the captchas were causing me to take longer than that.

Glad I could help Justin please accept the answer if you feel it's appropriate. Also could you elaborate what you did? Did you increase the amount of tries before Captcha?


Sorry, Atlassian wouldn't let me respond because I don't have enough points to make more than a couple comments per day.

Yes, for testing I increased the amount of tries before captcha to 100 and then I was able to lock the account.  Then once I figured out that it was possible to lock the account I found the OpenLDAP ppolicy setting pwdFailtureCountInterval and set it to 0 (changed from 30) so that failed attempts don't expire after 30 seconds and 5 consecutive failed attempts will lock the account, no matter how long apart they are. Then I lowered the captcha setting back to its original value of 3.

That sounds great I will try to bump your points little smile

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,174 views 5 10
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you