Entering Wrong Password in OMA Can Cause User Account to Get Locked
(Doc ID 2887845.1)
Last updated on AUGUST 04, 2022
Applies to:
Oracle Utilities Network Management System - Version 2.5.0.1.0 to 2.5.0.2.0 [Release 2.5]Oracle Network Management for Utilities - DMS - Version 2.5.0.1.0 to 2.5.0.2.0 [Release 2.5]
Information in this document applies to any platform.
Symptoms
On : 2.5.0.1.0 version,
ACTUAL BEHAVIOR
---------------
OMA heartbeat can lock an account with invalid credentials
An issue was found where an account can get locked in Active Directory with an invalid password.
If you try your password and type it incorrectly and get the invalid password message, then leave the OMA application open with the invalid password message displayed.
The heartbeat will keep trying to connect with the bad credentials until the account is locked, unless you put in the right password or close OMA before the retry count gets to 10 or you successfully login before the retry count gets to 10.
The heartbeat seems to try about every 20 seconds. The window is short before an account will be locked.
Accounts should not get locked if the operator enters invalid credentials
The issue can be reproduced at will with the following steps:
1. Attempt to login using a wrong password
2. Wait about 5 minutes
3. Attempt to login again,
the account will be locked
Changes
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 |
| Changes |
| Cause |
| Solution |
| Fix Description |
| Migration |
| References |