My Oracle Support Banner

Unable to Temporarily Allow Users to Login Once Maximum Number of Allowed Attempts is Reached (Doc ID 2099431.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Adaptive Access Manager - Version 11.1.2.0.0 and later
Information in this document applies to any platform.

Goal

You have set up rules in Oracle Adaptive Access Manager (OAAM) to block a user whenever he/she reaches maximum number of allowed attempts (i.e. 3 times) while authenticating using KBA questions and Email/SMS OTP. The rules work fine and are blocking the user whenever the maximum attempts counter is reached when authenticating using KBA questions and Email/SMS OTP.

However, users are not able to login to the system even after you reset the user by creating a Case using the "Customer(ALL)" option in OAAM Admin console. After resetting user profile in OAAM, users are unable to login and the status is still shown as "Disabled" in session details. Why can I not reset these users so they can login?

Solution

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
Goal
Solution


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.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.