LSF Security Error when trying to assign multiple rmid records the same requester number

We just updated our Test environment to ENV 10.0.9 and MSP 10.0.7 and are now seeing an issue in LSF Security where when we try and edit a requester id for a user we see "Lawson Security Error: Please check log files for details Error: Cannot link Identity for Resource. Original Exception: Assigning multiple RMIDs to this user is not allowed for service TST10_REQUESTER". We only get this error if the requester number we try and assign is already being used by another user. We have always had multiple users for one requester number and never had this issue, so I am assuming it is either a bug or something we missed in our updates.

Can anyone already on ENV 10.0.9 tell me if they are seeing this same issue? I have a ticket open with support but not getting a lot of response back yet.

Note: I did check LDAP and dumped the service identities for our Requester service and this is not an issue with the rmid record (user name), but more of an issue where the requester number itself is now one to one vs one to multiple.

Thanks in advance.

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

Just in case anyone else is like us and needs to be able to assign a one to many on the service identities (like RQC and/or EMSS), there was a change in this new version that changed the behavior to only allow one to one. The JT was JT-1027637. It doesn't give good description of this new behavior, so you would never know this change would occur.

robert-canham

So they're saying this is working as designed? Did they give a reason why this behavior is not allowed? We have it set similarly so that requesters in the same department have the same requester id so they can see all of the department requisitions.

unknown

They said it was done by the security development team to fill a gap in security that they felt was necessary. We have two LSFCT patches that we will have to back out to revert back to the old functionality. The person I am working with is still talking to development so I don't know if they will consider changing this back or not. Just didn't want anyone to go through what we did trying to figure out what happened.

unknown

Has Infor made a determination about changing this back to the way it worked? We can't move forward with patching production for another issue because of this.

Copyright © 2025 Infor. All rights reserved.