Unable to Log into OTM After Changing a Users Password via the UI or using update_password.sh
(Doc ID 2865385.1)
Last updated on SEPTEMBER 26, 2023
Applies to:
Oracle Transportation Management - Version 6.3.1 and laterInformation in this document applies to any platform.
Symptoms
After changing a user's password in the UI or using the update_password.sh script the user is unable to log into OTM.
The following message may be displayed.
The account for <UserGid> has been locked out due to disuse or suspicious activity. Please contact your system administrator.
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 |
References |