Bad Password Count Cached in 220.127.116.11.0
(Doc ID 1544532.1)
Last updated on MARCH 08, 2017
Applies to:Oracle WebCenter Portal - Version 18.104.22.168.0 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?
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|