
00u7x0o76dsKf8UMA0h1.4734452338982737E12 (Customer) asked a question.
Hi,
I ran into a scenario, where if user tries to reset password and uses his/her existing old password. Okta is unable to set the password. Even when the policy doesn't enforce policy history at all.
Is this a valid behaviour, so should anything specific need to be setup by Okta admin to allow it.
Thanks.

AD mastered or Okta mastered?
Its Okta mastered.
ok if it is an okta password and with those settings, that shouldn't be happening, especially with things like common passwords and password history being unchecked.
is there any policy in the list taking higher priority above this one that is overriding it?
Other option is raising a case with Tier 2 support to look at it further.
We have 4 policies but the one enforced to the certain group of users is attached below.
I have also attached snapshot of policy above this one.
My understanding is that priority is seq from top to bottom ?
Thanks.
[cid:image001.png@01D67C8A.CE79FB00]
[cid:image002.png@01D67C8A.CE79FB00]
That's right, top to bottom is the priority sequence. I am unable to see the images, can you attach again?