Prev
Next
Forums User Experience Lawson Smart Office

LSO connection refused

 8 Replies
 0 Subscribed to this topic
 11 Subscribed to this forum
Sort:
Author
Messages
msjmg111
Veteran Member
Posts: 74
Veteran Member
2/20/2013 2:01 PM
    I’m currently working on a Smart Office install and am having an issue connecting to the S3 application server.  I’ve installed the latest versions of LCM, Grid, DSSO, DSSOSessionProvider, and LSO and when I try to launch the client it returns an authentication error.  I set logging to debug and found that my HTTPS connection is being refused by the application server.  The Protocol on the app server is set to use HTTP only so I’m wondering if I need to make any changes on the app server to get LSO to connect?  Also, I installed a self-signed certificate on the LSO server, do I need any certificates on the app server?
    msjmg111
    Veteran Member
    Posts: 74
    Veteran Member
    2/20/2013 8:42 PM
      Sorry for the impatience but I’m stuck and have not found any documentation to assist me in getting this resolved. If you have LSO working with LSF can you tell me if your PROTOCOL_ASSERT in SSO set to Use HTTP only or HTTPS for logins only? I've checked and rechecked and the only error that I found in the logs is the following:
      Connection to https://lsfappserver.myco.com:19006 refused
      Since our protocol is set to Use HTTP only, I’m wondering if this is the problem. Any suggestions are welcome.
      JimMNH
      Veteran Member
      Posts: 60
      Veteran Member
      2/20/2013 9:06 PM
        You're launching LSO? Did you try a shortcut to http://lsfappserver.myco....erver.myco.com:19006 ?
        JimMNH
        Veteran Member
        Posts: 60
        Veteran Member
        2/20/2013 9:07 PM
          Mouse over that and you'll see the full URI
          msjmg111
          Veteran Member
          Posts: 74
          Veteran Member
          2/20/2013 9:47 PM
            LSO is on a different server (http://lsoserver.myco.com) and DSSOSessionProvider is trying to connect to my application server (http://lsfappserver.myco.com). Yes, I'm launching LSO and the shortcut (http://lsoserver.myco.com...rver.myco.com:19006) gives me the same connection refused message in the grid-node-DSSO Session Provider-5940.log (in debug mode).
            B. Smith
            Basic Member
            Posts: 8
            Basic Member
            2/21/2013 3:16 PM
              *Note we put all components on the same server for our lab test * Did you run ldapTest, ldapTest , ldap user password, tests in the LifeCycle manager post install steps to validate that the ldap was connected and communicating? Sounds like the DSSO isn't talking to the LDAP.
              msjmg111
              Veteran Member
              Posts: 74
              Veteran Member
              2/21/2013 4:09 PM
                I ran those tests (and just reran them) and they all check out just fine. There is a page (http://lsoserver.myco.com:19005/grid/info.html) that has several links and when I select https://lsoserver.myco.com:19006/auth/ (or /sso or /ssoconfig) I get an Error 403 Forbidden. Can someone tell me what is supposed to be on that link?
                msjmg111
                Veteran Member
                Posts: 74
                Veteran Member
                4/15/2013 6:42 PM
                  Just an update to this issue... In talking with a Lawson resource, I found that the DSSOSessionProvider (I believe it was 2.1) I had installed has a problem with LSO 10.5. I downgraded the session provider to 1.3.12 and everything is working. Thanks Jim and B. for trying to help me out.
                  Chesca
                  Veteran Member
                  Posts: 490
                  Veteran Member
                  10/15/2014 12:27 PM
                    Hello msjmg111,

                    Was this a new install or did you replace your session provider with DSP? We have Windows Session install into LCM and are trying to replace it with DSP 2.0. I updated DSSO 2.0.4 via CCSS in LCM and then I get an error when I try to register the DSP. I am confused about how to proceed next, should I install the DSSO componet or DSSO Session Provider, or DSP?


                    We are on LSO version 10.0.5, ESP 13, security 9, LCM 9.1.11.0