Bad Password Count Cached in

(Doc ID 1544532.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle WebCenter Portal - Version and later
Information in this document applies to any platform.


Active Directory (AD) bad password count is used to verify if a user is locked out (due to too many incorrect password entries) but it seems to be cached as the count stays at zero even when AD shows a higher number.

The code used is the following:

Is there a way to bypass this cache to make sure that the AD bad password count retrieved is always up-to-date?


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms