Last updated on JUNE 09, 2017
Applies to:Oracle Network Management for Utilities - DMS - Version 220.127.116.11 and later
Oracle Utilities Network Management System - Version 18.104.22.168 and later
Information in this document applies to any platform.
Valid username and password gives "User failed to be authenticated."
When a particular user ( one of a small handful of specific users ) launches Web Workspace, Config Assistant, Model Management, etc. and then enters their username and password, instead of an immediate "OK, starting the application", or an almost immediate "invalid username or password" message, it takes about 30 seconds to give "invalid username or password".
Both the username and password were verified to be correct and the user account is not locked.
2017-05-25 15:19:40,787 [pool-2-thread-4] WARN com.splwg.oms.client.login.LoginHelper: javax.naming.AuthenticationException: User failed to be authenticated. [Root exception is java.lang.SecurityException: User failed to be authenticated.]
cache: MemoryCache: removed entry http://nms-server:7003/nms/ModelManagement.jnlp
A new weblogic server for NMS was being tested before being pushed into production. The configuration was not copied from the old weblogic server.
During the previous year, they had encountered an issue with one of their LDAP servers. They replaced the bad server and changed their LDAP configuration to "Limited".
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms