View Single Post
  #1 (permalink)  
Old July 6th, 2007, 16:40
nkrantz nkrantz is offline
Junior Member
 
Join Date: Jul 2007
Posts: 4
Thanks: 2
Thanked 0 Times in 0 Posts
Groans: 0
Groaned at 0 Times in 0 Posts
Rep Power: 0
nkrantz is on a distinguished road
Unhappy javax.security.auth.login.LoginException...

Hi,

I have just completed my first installation of OTM 5.5.x on our test server. Most of the installation steps went smoothly, even though a more comprehensive installation guide would be nice.


However, when I try to launch the application through my browser, I get the following:
Code:
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.<init>(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.<init>(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)
I have been searching this forum and googled for the same error. I have double checked so that the user actually exists and that the password is base64 encrypted as CHANGEME. Servers has been restarted. I have double checked the version of WebLogic also (saw some note about a common issue was the wrong version) and we're on SP4.

Any ideas?

Thanks,
Niclas
Reply With Quote