You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
We have recently moved from using an Internal Crowd Directory to using a Microsoft AD connector for all of our Atlassian users.
I've just had a report of a user who changed thier password in AD and then tried to login to JIRA with the new password. This failed (I guess it hadn't syncronised yet). I performed a full syncronisation with "incremental sync" disabled. The user reported that thier AD account was locked, but after being unlocked in AD they could log into Jira.
Can failed password entries in Crowd/JIRA etc cause an AD account to be locked when syncronisation occurs?
And are password updates not included in incremental syncs?
I have left "incremental sync" disabled for now. Would password changes be reflected quicker in the Atlassian applications if I disabled the Cache in Crowd as well? We have about 1800 users.
Thanks,
Ben
Same issue here.
There should be similar password policies like internal crowd directories – with at least maximum password attempts.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.