Landmark HTTP to HTTPS switch for ADFS

has anyone switched Landmark and LSF to HTTPS ? if so how do you change the inbasket address to point to HTTPS? i got lsf going and landmark both are updated with HTTPS and secure ports in config files. everything else is updated just Inbasket is still pointing to HTTP address.

here is what i have done.

after .cfg files updated re ran the install to redeliver files for all apps in landmark,

with correct https ports in place ran the iss sync

endpoints and services in landmark are updated

restarted few times in between all of this.

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

You may have looked at this - but have you checked the Inbasket Landing Page in Rich Client setup?

unknown

Hi Kyle

I saw that setting there but it wont let me modify the url. which led me to believe that i need to run through the steps above.

russel-cornelson

I am on my cellphone car pooling to work so please excuse typos.

The inbasket link is dynamically built when you log into portal. Portal login calls servlet/Profile. That servlet connects to Rmi using ipaddress inside Logan table WFEVTSERV. From there it connects to grid and looks at the user profile and the DATAAREA.LPA.LPA service.

Ensure that service, the BPM service and LPA.LPAADMIN service are set to HTTPS.

P.S

servlet/Profile caches the response so make sure you do an IOSCacheRefresh after any change.

P.S.S

LPA grid nodes cache the LPA.LPA service urls at startup to dodge a security performance issue. So after changing the services restart these nodes. Do this before the iOS cache refresh.

That shotsokve the problem for you

russel-cornelson

If this doesn’t fix your issue, please open a ticket with IPA support and I can help you figure it out

unknown

Hi Russel

i tried that but not getting very far. i have opened an incident.

unknown

Thanks Russel for Helping out.

The issue turned out to be SSOPV2 service properties in Landmark had http address. we updated that to HTTPS and port to 443, restarted the LPA node which resolved the problem.

Copyright © 2025 Infor. All rights reserved.