Cannot login OTM after migrating to version 5.5 or changing GUEST.ADMIN password from the default value of CHANGEME (Doc ID 422201.1)

Last updated on NOVEMBER 17, 2016

Applies to:

Oracle Transportation Management - Version 5.5 and later
Information in this document applies to any platform.
***Checked for relevance on 13-Jan-2014***


Symptoms

-- Problem Statement:

OTM Users migrating to OTM 5.5 may report the following error is being generated when they try and log into the system. The same error will be generated if the GUEST.ADMIN password is changed from the default value of CHANGEME.

javax.security.auth.login.LoginException: javax.security.auth.login.LoginException: java.lang.SecurityException: User: GUEST.ADMIN, failed to be authenticated.

javax.security.auth.login.LoginException: javax.security.auth.login.LoginException: java.lang.SecurityException: User: GUEST.ADMIN, failed to be authenticated.
at glog.database.security.jaas.ClientLoginModuleImpl.login(ClientLoginModuleImpl.java:50)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:675)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:129)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:610)
at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:607)
at javax.security.auth.login.LoginContext.login(LoginContext.java:534)
at glog.database.security.jaas.AuthenticationContext.login(AuthenticationContext.java:95)
at glog.util.remote.NamingDirectory.(NamingDirectory.java:783)
at glog.util.remote.NamingDirectory.get(NamingDirectory.java:199)
at glog.util.remote.NamingDirectory.getForGuest(NamingDirectory.java:307)
at glog.util.remote.NamingDirectory.get(NamingDirectory.java:115)
at glog.util.remote.NamingDirectory.get(NamingDirectory.java:126)
at glog.util.remote.SessionBeanHomeInvoker.(SessionBeanHomeInvoker.java:26)
at glog.util.remote.NamingDirectory.get(NamingDirectory.java:170)
at glog.util.remote.NamingDirectory.get(NamingDirectory.java:225)
at glog.util.remote.NamingDirectory.getForSystem(NamingDirectory.java:283)
at glog.util.remote.NamingDirectory.getForSystem(NamingDirectory.java:316)
at glog.util.remote.NamingDirectory.getForSystem(NamingDirectory.java:320)
at glog.util.uom.UOMLoader.loadFromServer(UOMLoader.java:92)
at glog.webserver.util.BaseServlet.service(BaseServlet.java:585)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at glog.webserver.screenlayout.ClientSessionTracker.doFilter(ClientSessionTracker.java:54)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)

Similar errors may be noted in the console logs for tomcat and weblogic.

From the Tomcat console log:

INFO | jvm 1 | 2007/10/10 09:55:48 | javax.security.auth.login.LoginException: javax.security.auth.login.LoginException: java.lang.SecurityException: User: GUEST.ADMIN, failed to be authenticated.
INFO | jvm 1 | 2007/10/10 09:55:48 |
INFO | jvm 1 | 2007/10/10 09:55:48 | javax.security.auth.login.LoginException: javax.security.auth.login.LoginException: java.lang.SecurityException: User: GUEST.ADMIN, failed to be authenticated.
INFO | jvm 1 | 2007/10/10 09:55:48 | at glog.database.security.jaas.ClientLoginModuleImpl.login(ClientLoginModuleImpl.java:50)
INFO | jvm 1 | 2007/10/10 09:55:48 | at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
INFO | jvm 1 | 2007/10/10 09:55:48 | at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
INFO | jvm 1 | 2007/10/10 09:55:48 | at javax.security.auth.login.LoginContext.invoke(LoginContext.java:675)

From the weblogic console log:

INFO | jvm 1 | 2007/10/10 10:01:01 | <Oct 10, 2007 10:01:01 AM EDT> <Critical> <Security> <BEA-090403> <Authentication for user GUEST.ADMIN denied>
INFO | jvm 1 | 2007/10/10 10:01:01 | javax.security.auth.login.LoginException: javax.security.auth.login.LoginException: java.lang.SecurityException: 090403
INFO | jvm 1 | 2007/10/10 10:01:01 |
INFO | jvm 1 | 2007/10/10 10:01:01 | javax.security.auth.login.LoginException: javax.security.auth.login.LoginException: java.lang.SecurityException: 090403
INFO | jvm 1 | 2007/10/10 10:01:01 | at glog.database.security.jaas.ClientLoginModuleImpl.login(ClientLoginModuleImpl.java:50)
INFO | jvm 1 | 2007/10/10 10:01:01 | at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
INFO | jvm 1 | 2007/10/10 10:01:01 | at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)

Cause

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