Security issues after LSF-Landmark federation

Federation not ready for prime time. Still lots of bugs.

That may be true, but since I am going to be installing LPA, I don't have any choice but to federate, do I?  The install doc leads me to think that way.

Yes, to install LPA, you will need Landmark runtime, which means you should federate between LSF and LMK. However, the federation is still in its infancy, and has a long way to go (for instance, sync'ing is not automatic, the combined LSF/LMK security admin client doesn't work, etc.). So if you're not in a hurry, you might not want to rush it. To troubleshoot your issues, let's start with MSCM: - did you install updated DSSO/DSP on that server to match what is in your federated LSF?

No, and when I opened my case with Lawson/Infor, that was one of my specific questions - do I need to do something different with DSSO?  The answer was no - you should be fine.  Didn't sound right, but when I encountered other problems as well, I figured maybe that was not the issue.  My MSCM is on the same Unix server as my LSF environment - not on a separate Windows server like a lot of clients do.

Which version of MSCM?

9.0.1.2 patch 10

Make sure you have the exact same version of the sec-client.jar on all systems

Update - I uninstalled Landmark 10.0.2 and installed 10.0.3 CU 12.  Running into issues again with federation, but somewhat different this time.  I suspect that my configuration changes in lsservice.properties (on both the Landmark and LSF servers) is not correct, in particular I am not sure what port numbers I should put in those lines I am adding to the files.  Any ideas?

RESOLVED - at least for my version - it turns out that the documentation for federating the 2 is incorrect.  In the section where it says to add 5 lines to your lsservice.properties file on LSF, you really only need the first 2 lines.  And you don't need to make any changes to the Landmark lsservice.properties file.  I am now federated and it's looking good so far....