Why Does Configured Password Policy Allow BINDs when Subsequent Requests are Rejected with Error 53
(Doc ID 1996252.1)
Last updated on MARCH 29, 2019
Applies to:Oracle Directory Server Enterprise Edition - Version 5.2 and later
Information in this document applies to any platform.
A custom password policy has been created and it has been applied to a specific user entry to force a password reset. When the user authenticates, the bind is successful (no error is returned), but subsequent operations on the same connection return the expected err=53. Why does the authentication/bind not fail with the same error 53? Below is the custom password policy being used...
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document