Use ActorId (employee id) instead of UPN for authentication

We are in the process of installing our first Landmark application and in doing so will also be moving ISS and Azure for single sign on. We have run into issues using the UPN (email) when there is a change to the email address - our UPN is not correctly assigned until after an Outlook 365 license is obtained and/or when employees have a name change. Infor provides the ability to use the ActorId for authentication (listed in the dropdown) so we configured Azure to pass the employee id in ActorId - our employee id's never change so thought this would be a better option than trying to use email address that can change. We made the change to Azure, changed the SSOP to employeeid, tested and it appeared to make the authentication but we got a security related error in regard to LSF. Has anyone attempted this authentication method and if so, what configuration change needs to be made to LSF to login with ActorId? Thank you!

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Accepted answers

All comments

lmerrill

We changed our UPN from emailID to actorID a couple of years back with the help of ICS (Dennis O'Connor). Was a pretty smooth change. Working with no issues since then.

moellerg

Just curious. What kind of issues were you having with using your email id?

deanna-plant

Hello Sreedevi! Are you using ADFS or Azure for your authentication? Our consultant checked with Dennis and he only recalls getting the employeeid to work with ADFS, not Azure. There has to be a way to accomplish this!

deanna-plant

We are passing new hire accounts from AD to Lawson security using loadusers/secadm - at the time of hire we don't have their 356 license therefore it is not giving them a valid UPN until later. We aren't able to automate the "change" to the UPN in Lawson security once it is updated in AD. IFS gets updated to the corrected email address automatically but ISA does not so they do not match up.

deanna-plant

Correction...the UPN is getting updated in Lawson security after the valid UPN is updated in AD but the SSOP will not automatically update. That is why we were looking at a static value (employee id) for authenticating.

mbozenik

This probably isn't much help, but we're looking into switching from ADFS to Azure for authentication as well. We have a similar issue with the UPN. In our case we are transitioning to O365 and as users are migrating the UPN changes. It doesn't appear to be a factor for ADFS, but it does for Azure. We're still testing and I'm waiting for everyone to be migrated so this isn't an issue. In our test environment I've just been updating the <USER ID="lawtest1@xxx.com" attribute in the loaduser xml file and running loadusers. For us we'll still trying to figure out the Azure requirements. Again ADFS works fine, but Azure not so much. I'm curious if you had to add custom claims to your Azure application being published Infor?

Copyright © 2025 Infor. All rights reserved.