Announcement

Collapse
No announcement yet.

javax.security.auth.login.LoginException...

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • 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

  • #2
    Re: javax.security.auth.login.LoginException...

    Niclas,

    Okay - it sounds like you've covered the basics:
    • You're using WebLogic 8.1SP4
    • You haven't changed the default password of the GUEST.ADMIN user
    Just to confirm on the second note - you shouldn't have had to change the password in your tomcat.conf, weblogic.conf or database as it should already be setup as the default of CHANGEME.

    Were there any errors in your Install Log files - particularly on the OTM Web and App servers? You can find more info for verifying here:The next most common issue (which usually shows up in the log files) is that either the WebLogic jar files weren't able to be copied into the OTM installation, due to file permission issues. You can check this by ensuring that the following files exist on your OTM Web and App servers under <otm_home>/glog/gc3webapp/WEB-INF/lib/3rdparty/ :
    • weblogic.jar
    • webservices.jar
    • xmlx.jar
    Another possibility is that the OTM java security jars weren't able to be copied into the WebLogic directory by the root.sh script on the OTM App server installation. In this case, you should have the following files in your <bea_home>/weblogic81/server/lib/mbeantypes/ directory:
    • gc3authenticator.jar
    • gc3authorizer.jar
    Finally, did you download and install all of the 3rd party jar files into OTM? These are actually required for full functionality, though Oracle won't allow them to be distributed with OTM, due to licensing issues.

    If you can check these and report back, I'll help further.

    Thanks,
    Chris
    Chris Plough
    twitter.com/chrisplough
    MavenWire

    Comment


    • #3
      Re: javax.security.auth.login.LoginException...

      Chris,

      Thanks for your notes. I will check them all in detail once I have access to our development server (Windows 2003 server)

      I added the base64 encoded string of the password, as a just in case, as I got the identical error message as that issue caused.

      I did download an install the required 3rd party things. But there might have been something I have missed.

      Also thinking of re-doing the full implementation of OTM, just to make sure I get everything right, but will of course check your tips first!

      Best regards,
      Niclas

      Comment


      • #4
        Re: javax.security.auth.login.LoginException...

        Hi,

        So, I couldn't wait.
        Were there any errors in your Install Log files - particularly on the OTM Web and App servers?
        No errors at all, no warnings.

        The next most common issue (which usually shows up in the log files) is that either the WebLogic jar files weren't able to be copied into the OTM installation, due to file permission issues.
        All files were there.

        Another possibility is that the OTM java security jars weren't able to be copied into the WebLogic directory by the root.sh script on the OTM App server installation.
        Both files were present

        Finally, did you download and install all of the 3rd party jar files into OTM?
        As mentioned, I believe I did this, but I am unsure how to validate.

        I do remember that I got some messages during all database setup (importing table spaces and so on...) Any good tutorial on how to validate this?

        Thanks,
        Niclas

        Comment


        • #5
          Re: javax.security.auth.login.LoginException...

          Just an update for OTM v6.x -- the security integration jars were merged into otmSecurityProviders.jar. It gets copied into the $BEA_HOME/bea/weblogic92/server/lib/mbeantypes directory by the root.sh script and is required to initialize OTM's security.

          --Chris
          Chris Plough
          twitter.com/chrisplough
          MavenWire

          Comment

          Working...
          X