Installing DSSO

Hi Matt,

If you are using DSP and have the required JTs in place for LSF 9.0.1.12 (see the Security Readme file on the DSP download page), then you do not need to install LCM on your LSF server.

It sounds like the DSP base installation wasn't successful if the /java folder is missing - you should see {DSSOInstallDir}\java after installing DSP and within this directory you'll see the jar and thirdparty files that are pulled from your LSF server. Make sure to select the option for 'manual deployment but create service' and populate your DSSO router ports under the 'application server properties' section when you install DSP in LCM.

I'd also recommend double checking your Lawson Security Server values - I seem to recall a scenario where if there was a typo on these values that the installer didn't indicate a failure, but the files for DSSO weren't created.

HTH!
Anna

Thanks Anna. I have both installed now. I was also able to install ISO. My problem now is security isn't working for Smart Office. Can anyone guide me to what I need to add to Lawson Security to make my install of Smart Office work? I see the Identities for DSSO and the server, but after populating them nothing occurs. I don't see any manuals on this either. Any direction would be appreciated.

Cheers.
Matt

Anna,
Is the DSP installed on the LCM/Grid box or the LSF box.  Keeping in mind LSF is AIX and LCM/Grid is Windows.  I am wondering if this is where my mistake was made.  I installed the DSP on the LCM/Grid box.  Any help you can offer is appreciated.

Thanks.
Matt

Hi Matt,

You're right on track - DSP would be installed into LCM and not on the LSF box from Smart Office.

When you say that security isn't working, I'm assuming that this means that you are unable to authenticate/log in to Smart Office?  A few things that I would start with are:

1- Make sure that you have the latest DSSO Session Provider patch in place (in LCM, Actions > Retrieve Fixes, select DSSOSessionProvider20 channel and retreive and apply the latest patches).

2- Turn on the log for the DSSO Session Provider, replicate the error when logging in and check the DSSOSessionProvider log for more information (in LCM, Grid Management Page > Logging > Log Levels > check the boxes for 'Debug' and 'Trace' under the DSSOSessionProvider). 

There really isn't any set up that's needed on the LSF side for users to be able to log in to Smart Office; if the user can log into Portal, then they should be able to log into Smart Office with the same security.  The DSSOSessionProvider log is usually pretty helpful in determining why authentication is failing.

HTH!
Anna

Thanks again.

It appears that the Truststore is not correct.  There is no ts.ks file or ts.pwd file.  I attempted to update the Truststore and it will not update because of this problem.

Does anyone know when you install DSSO component are you suppose to reference the Security server address or the LSF address?

Once again thanks for the help.
Matt

I have corrected the Truststore issues.  Now I am receiving:

java.lang.NoSuchMethodError: com.lawson.security.authen.SessionCache.getSessionCache(Ljava/lang/ObjectLcom/lawson/security/authen/SessionCache;
at provider.webapp.AuthenticationServlet.execute(AuthenticationServlet.java:174)
at provider.webapp.AuthenticationServlet.doGet(AuthenticationServlet.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at com.lawson.security.authen.BaseAuthenticationServlet.service(BaseAuthenticationServlet.java:280)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:527)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:423)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:456)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:225)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:930)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:358)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:183)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:866)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:245)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113)
at com.lawson.grid.http.jetty.HttpServerImpl$3.handle(HttpServerImpl.java:353)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113)
at org.eclipse.jetty.server.Server.handle(Server.java:337)
at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:595)
at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:1038)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:549)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:211)
at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:424)
at com.lawson.grid.http.jetty.StreamConnector$StreamEndPointExecutor.run(StreamConnector.java:344)
at com.lawson.grid.http.jetty.StreamConnector.executeOnCurrentThread(StreamConnector.java:245)
at com.lawson.grid.http.jetty.StreamConnector.invoke(StreamConnector.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.lawson.grid.proxy.ProxyServerImpl$ProxyRequestThread.invoke(ProxyServerImpl.java:2775)
at com.lawson.grid.proxy.ProxyServerImpl$ProxyRequestThread.processRequest(ProxyServerImpl.java:2556)
at com.lawson.grid.proxy.ProxyServerImpl$ProxyRequestThread.runThread(ProxyServerImpl.java:2479)
at com.lawson.grid.util.thread.PooledThread.run(PooledThread.java:135)
at java.lang.Thread.run(Thread.java:662)

Hi Matt,

Do you see 'sec-client.jar' in {DSSOInstallDir}/java/thirdParty on your LCM server? The method 'getSessionCache' in in the sec-client.jar file that is pulled from the LSF server during the installation of DSSO in LCM.

If you see this file, this could either be a (1) versioning issue with the file (i.e. the method isn't in your sec-client.jar) or (2) the path that grid is looking for to find sec-client.jar is incorrect. For the latter, you can verify your classpath entries in the Grid Management page for the DSSO application (I believe it's under application properties) or you may see the classpaths output into the logs if DEBUG/TRACE is enabled.

-Anna

Actually, thinking about this more - usually a NoSuchMethodFound indicates that the class file (SessionCache) is found and, therefore, sec-client.jar is found.

I would check to see that you have the JTs for LSF in place (check the DSP readme file) and that you have the latest DSSO Session Provider patches installed.

Actually, thinking about this more - usually a NoSuchMethodFound indicates that the class file (SessionCache) is found and, therefore, sec-client.jar is found.

I would check to see that you have the JTs for LSF in place (check the DSP readme file) and that you have the latest DSSO Session Provider patches installed.

Actually, thinking about this more - usually a NoSuchMethodFound indicates that the class file (SessionCache) is found and, therefore, sec-client.jar is found.

I would check to see that you have the JTs for LSF in place (check the DSP readme file) and that you have the latest DSSO Session Provider patches installed.

I don't see where the java class path is defined.

Thanks for all the help Anna. It is much appreciated.

Never mind I found it.

Hi Matt,

I'm betting that it's pointing to the correct location and that the file exists. What version of the DSSO Session Provider are you using? Have you downloaded the patches from CCSS for the DSSO Session Provider?

I meant to send this a couple days ago. A big thank you for the help. Patching DSSO and the Grid corrected the problem. Version 2.0.4 seemed to contain the fix needed.

Cheers.
Matt

Glad to hear it! Thanks for the follow up.

Hello All,

Just wanted to resurect this thread to ask a question about something Matt addresses above. Seems I have a "java" issue when installing my DSSO base because I don't have a "java folder under my "{DSSOInstallDir}" as Anna references above. My session provider logges the following when it tries to start:

java.io.FileNotFoundException: C:\dsso\dsso_iso\java\jar\secondary\sso.war (The system cannot find the path specified)

There is no C:\dsso\dsso_iso\java folder. When installing the DSSO base - my "DSSO root install folder" is called "c:/dsso/dsso_iso". The Java home is "C:/glassfish3" and Perl home is "C:/Perl64". I've even pointed these properties all the way down to the bin locations for both Java and Perl, still no luck.

Any thoughts on where to look first?

Thank you all,
Jared

Hi Jared,

The installation should create a /java directory that contains jar files that the install scripts retrieve from your LSF server, like the sso.war that it is 'complaining' about.

When you ran the DSP installer, did you select 'Manual install but create service'? This is the first piece I would check. Then, double-check your LSF hostname and security ports populated during the install (install.cfg) - compare these values to those in lsservice.properties in LAWDIR/system on your LSF server. Are the values correct? In the past, I've seen the installation complete when the servername is incorrect or, depending on the version of DSP, if there is a dash in the servername. Does your host have a dash in the name?

I hope this helps!
Anna

Thank you Anna for taking the time to respond to this post. "Manual install but create service" was chosen as instructed when installing DSP. Host name is without dashes and security ports match what my lsservice.properties has.

When defining the "Lawson Security Evnironment", under "OS Service Identity", I'm having trouble getting my head around what the "Identity name" and "Domain" should be. Since this information is supposedly coming from the security environment on our LSF server, what are these fields requesting?

Much appreciated...
Jared

I was hoping you could tell me how you got the below resolved .... I am having the same issues as you:

2. I get the DSSO router setup, and run the DSP install and it appears to be installed, but when I go to deploy the DSSO I get the following error. My theory is that I'm either not getting the DSP installed properly or I have some problem when installing DSSO.

Task Deploy DSSO to Grid finished with an error: Failed to run script C:/Program Files (x86)/Lawson/LifeCycle Manager/Server/products/DSSOSessionProvider_2.0/templates/register_dsso_as_grid_app.vm

Hi Chris & Jared,

Jared: The identity and domain are the account that will be tied to your OS service.  Typically, for Smart Office, I just leave this as is (System/servername) - this means that the LocalSystem account on the Smart Office server is used as the account.

Chris: Do you see that all of the files from the LSF system were brought over when you installed DSP in LifeCycle Manager?  For example, go to $DSSO_HOME and look for /java/thirdParty - does this directory exist with files inside of it?  The C:\lawson\dsso directory will also contain logging that can be useful for troubleshooting installation issues with DSSO.

Hope this helps!

Anna

 

 

Hi Anna, we were now able to log into LSO ... However can not acess any Lawson forms, do you know why or what we can check first?

Hi Chris,

I'd start with installing the latest Smart Office hotfixes for your version.

If that doesn't resolve the issue, I'd recommend doing a Fiddler trace and reviewing the HTTP requests for clues.  Another possible problem that I've seen (depending on your LSF patch level) is related to an LSA profile not being assigned a datasource.  The snippet below is from Xtreme:

Log into Lawson Security Administrator (LSA) and select Profile Management > Profile Assignment and review the datasources and corresponding profiles. If GEN, LOGAN or your productline is not assigned to a datasource, assign one using the 'User Profile' drop down at the bottom of the screen and press 'Assign'.

Good luck!

Anna

We got it ... Thanks Anna