The SSO services tag is missing.

 2 Replies
 0 Subscribed to this topic
 22 Subscribed to this forum
Sort:
Author
Messages
rockie12_us
Advanced Member
Posts: 32
Advanced Member

    On our LBI 9.0.1.6 install on Windows we keep getting this error in our Tomcat stdout.log file

    We use DSSO and have our portal bound to Active Directory...

    What is this error telling us?

    com.lawson.lawsec.authen.httpconnection.LHCException: getLogoutUrls: The SSO services tag is missing.
     at com.lawson.lawsec.authen.httpconnection.LawsonHttpConnection.getLogoutUrls(Unknown Source)
     at com.lawson.lawsec.authen.httpconnection.LawsonHttpConnection.doLogout(Unknown Source)
     at com.lawson.efs.security.roleprovider.SSORoleProvider.getList(SSORoleProvider.java:183)
     at com.lawson.efs.security.roleprovider.SSORoleProvider.listGroups(SSORoleProvider.java:150)
     at com.lawson.efs.security.authenticationprovider.SSOAuthenticationProvider.getUserContext(SSOAuthenticationProvider.java:276)
     at com.lawson.efs.security.authenticationprovider.SSOAuthenticationProvider.getUserContext(SSOAuthenticationProvider.java:232)
     at com.lawson.efs.security.authenticationprovider.SSOAuthenticationProvider.authenticate(SSOAuthenticationProvider.java:116)
     at com.lawson.efs.ssoa.SSOFilter.doFilter(SSOFilter.java:227)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
     at java.lang.Thread.run(Thread.java:534)

     

     

    Matthew Nye
    Veteran Member
    Posts: 514
    Veteran Member

      Its telling you the DSSO isnt working. .........

      Sorry, hard to say. Looks like a config file is male formed. First off, I would DEFINITELY upgrade LBI. Youre almost 2 years behind on upgrades and there have been major improvements. At a minimum you should get up to 9.0.1.10 as is a fairly painless upgrade, as opposed to 9.0.2.2.

      Ive heard rumors that DSSO doesnt work with tomcat but we recently had a client that said a Lawson consultant got it to work. I personally have only done it on WebSphere, which I strongly recommend you get there too. Makes for much easier administration, especially when you start getting errors like this.

      Sorry I cant give you anything concert here but keep posting back what you find and Ill do my best.

      hth
      matt

      If any of my answers were helpful an endorsement on LinkedIn would be much appriciated! www.linkedin.com/pub/matthew-nye/1a/886/760/
      rockie12_us
      Advanced Member
      Posts: 32
      Advanced Member
        Thanks for the reply....

        It appears as though the problem is solved in 9.0.2 our test server is running 9.0.2 and we do not have one of these errors. FYI
        Dean-O