Has anyone been able to automate update (remove, update roles/identity) existing users in a federat

Hi,

We are working on v10 upgrade testing environment, this is the first time we have been federated between S3 & Landmark systems. In v9 instance we had 2 separate processes maintaining security in S3 & Landmark. Both basically added new user, modified roles, removed roles & updated emails based on a changes file. With federation, we figured out how to use the list based sync utility. But it works only for new actor records or adding roles or email, it does not seem to remove roles or update email on existing actors. With the volume of changes & users in our environment, it would be hard to maintain a manual process to maintain changes. Due to the time it takes to sync, we also had to walk away from full sync, as it took 4 hrs or more.

So has anyone been able to automate the update/removal of roles/emails with list based sync ?

Thanks

Ratna

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

We created a flow that disables users and removes their roles on the S3 and Landmark side. We then have to run a list based sync. We use a Resource Update Node for S3 and a Landmark Transaction Node for Landmark.

unknown

So you would remove all roles, emails & unlink identity first. Then update S3 with roles (we use loadusers command) & then run the list based sync to get the updated data into LTM? I think that order makes sense, we use process flow currently so we should be able to figure that out.

One other question, if you don't mind. When we ran the list based sync, the identity didn't get created on the Landmark side. Do I need to specify identity needs synced somewhere?

Thank you very much for helping.

Ratna

unknown

No sure. If you need to replace roles and emails then I guess you would remove them first using a Resource Update Node and then use a second one to add them back in for S3. A list base sync will not create the identity on the Landmark side. I made the same assumption when I first started working with it. You will have to use a Landmark Transaction Node to add the identity. We only have a process in place for new employees at this point. We haven't figured you how to do it for name changes, etc. From what I can tell the only thing that a list base sync does is make it possible for the changes to show up in ISS. I may be wrong though. Hopefully someone else on this forum can give you more insight on how to handle making changes to existing employees.

jreese

Like JimY stated, the list base sync only gets the security to show up in ISS. When you enter changes directly into LSF it will update ISS but if you do it programmatically then ISS is not updated. At least that was what I was told when we first went to V10. We have a process that handles Hires and Rehires nightly on a schedule and we have a process that allows our Security Officer to enter employees in manually if they didn't process through the nightly flow successfully. We also have a process to handle Name Changes, based on how our Security Officer was handling manually, and we also have processes to handle updating terms and updating roles, groups and portal roles for Requesters and Requisition Approvers. In each case we handle the LSF and Landmark updates through individual nodes and run the list based sync for most to update ISS.

Copyright © 2025 Infor. All rights reserved.