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

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 Join to answer
Community showcase
Teodora [Botron]
Published Feb 15, 2018 in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

1,173 views 6 19
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot