What causes Crowd requiresPasswordChange attribute to become true?

Is there a list anywhere of what can cause the requiresPasswordChange attribute to flip? We were manually changing the passwordLastChanged attribute and soon after the requiresPasswordChange attribute changed to true. This doesn't seem to be the case, or even possible, but we don't know what else would/could change it. This was a service account that has some old jobs running using old passwords but we do not lockout accounts based on invalid password attempts in this directory. Does anyone know what else causes an account lockout? 

1 answer

1 vote

Not all directories support this attribute.

Internal directories automatically manage this attribute. If the user password is older than password_max_change_time (this is a configurable attribute of the internal directory), the next successful authentication will set the requiresPasswordChange attribute in the user.

Programatically, this attribute can also be set for all users by calling DirectoryManager.expireAllPasswords().

Suggest an answer

Log in or Sign up to answer
Community showcase
Asked Thursday in Jira Ops

I'm John Allspaw, Ask Me Anything about incident analysis and postmortems

I'm John Allspaw, co-founder of   Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...

5,356 views 21 17
View question

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