Oracle Identity Manager (OIM) Integrated with Oracle Access Manager (OAM) Locking User Throws: Error sending notifications oracle.security.am.common.exceptions.NAPException: Exception in connecting to server. Connection timed out
(Doc ID 2691952.1)
Last updated on JANUARY 20, 2022
Applies to:
Identity Manager - Version 11.1.2.3.0 and laterInformation in this document applies to any platform.
Symptoms
An admin user logs into Oracle Identity Manager (OIM) through Oracle Access Manager (OAM)
The admin user tries to lock a user
After several minutes the operation has still not completed and the same screen where asked to confirm if the account should be locked is still displayed (see above screenshot).
At some point ( X number of minutes) the operation completes and the user shows has locked in OIM (and LDAP backend).
If the user had a valid session, due to this issue, the session remains active in OAM as OIM was not able to notify OAM.
Because the session was not invalidated in OAM the user will still be able to navigate the protected resources until the session expires.
Cause
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
Symptoms |
Cause |
Solution |