DSSO Session Provider Install - LawsonGuru.com

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1375
Roger French	1315
mark.cook	1244

Chris

Advanced Member Send Private Message

Posts: 23

1/30/2014 5:46 PM

I am attempting to replace the LDAP Session Provider on our Smart Office Server with the DSSO Session Provider and am having trouble understanding the requirements.

It appears that the first step is the installation of the "DSSO base component" which I believe is the procedure in the "Distributed Single Sign-on Solution for Lawson Smart Office Installation Guide." I understand the Bouncy Castle requirements but then it apprears that it wants a Life Cycle Manager service installed on both the LSF and Landmark servers - we have Landmark federated to LSF. LSF is bound to AD for authentication.

So, does this make sense?

1. Configure Bouncy Castle on the Smart Office server
2. Install S3 components in LCM on the Windows 2008 Smart Office server
3. Install Landmark components in LCM on the Smart Office Server
4. Install an LCM service on our HP-UX LSF server
5. Install an LCM service on our Windows 2008 Landmark server
6. Install DSSO "base component" into LCM on the Smart Office server
7. Install the DSSO session provider in LCM on the Smart Office server:
    a. Install a new Grid router
    b. Install DSSO
    c. Install the DSSO Session Provider

John Henley

Posts: 3351

1/31/2014 3:52 PM

Man, this gets complicated

I don't see a need for Bouncy Castle on the SO server in your scenario, but otherwise you have the correct steps.

Chris

Advanced Member Send Private Message

Posts: 23

1/31/2014 4:29 PM

Thanks for your reply. Bouncy Castle was the one step I wasn't questioning - the Distributed Single Sign-on Solution for Lawson Smart Office Installation guide says "Bouncy Castle must be configured in the Java JDK installed on the Lawson Smart Office Server."

Regarding the complexity, when I talk to people at Lawson, I get the impression that they don't understand what they are doing to us - with LSF, Landmark, MSCM and Smart Office all running on different middleware stacks, the number of components that we have to install and manage and patch and upgrade is probably ten times what it was when we first installed Lawson 15 years ago.

John Henley

Posts: 3351

1/31/2014 5:05 PM

Yeah, and that doesn't even include Sharepoint and Workspace

Chris

Advanced Member Send Private Message

Posts: 23

2/4/2014 2:08 PM

And, if we aren't already having enough fun,

The component downloads aren't found where the documentation says they should be...

And they aren't named what they are supposed to be...

And there are multiple versions, none of which match.

David Britton

Veteran Member Send Private Message

Posts: 53

2/4/2014 3:29 PM

We are going through some of this with our upgrade to Lawson Security. When you enter a ticket or call support to ask about missing documents/downloads they tell you you should hire Lawson Professional Services to do the work. When we point out all we are trying to do is locate a document referenced in a Knowledge base article (but which isn't there) they say if we attended Security Training or used Professional Services we would be told where the new document is.

Chris

Advanced Member Send Private Message

Posts: 23

2/6/2014 6:30 PM

I just got a LifeCycle Manager service up and running on our Landmark server. It looks like all the Landmark components and apps are now showing up within LCM - does this mean I can manage Landmark and Contract Manager upgrades and patches from LCM?

Chris

Advanced Member Send Private Message

Posts: 23

2/7/2014 1:57 PM

Uh-oh, I think I'm in an endless loop, step 7b looks like the same thing I already did in step 6????

1. Configure Bouncy Castle on the Smart Office server
2. Install S3 components in LCM on the Windows 2008 Smart Office server
3. Install Landmark components in LCM on the Smart Office Server
4. Install an LCM service on our HP-UX LSF server
5. Install an LCM service on our Windows 2008 Landmark server
6. Install DSSO "base component" into LCM on the Smart Office server
7. Install the DSSO session provider in LCM on the Smart Office server:
a. Install a new Grid router
b. Install DSSO
c. Install the DSSO Session Provider

fedenaj1

Basic Member Send Private Message

Posts: 10

8/29/2014 5:01 PM

Gurus! Chris, how did you get past this "endless loop". I'm working on step 6 of your list above right now. When you're providing the "web application server" properties, you are asked for the Http and Https ports of the dsso router you created when installing the router for the DSSO session provider... Huh? I can't do that yet until I have the DSSO base in place.

What ports are being referenced here?

Thanks in adance all,
Jared

fedenaj1

Basic Member Send Private Message

Posts: 10

8/29/2014 7:34 PM

I was able to figure out what ports are required. I discovered how to install the DSSO Router that was specifically for my Session Provider, made note of the ports specified, and provided them to the base install. Now, I wish I could understand why I'm not getting a "java" folder under my {DSSOInstallDir}\{DSSOInstance-NameDir}\. My session provider log complains about the following:

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

Thanks Gurus...
Jared

John Henley

Posts: 3351

8/29/2014 7:48 PM

Did you copy DSSO jar from LSF and install it on the LSO server?