I opened a case with Lawson but not getting a definitive answer.
Since the CheckLS flag still exists in Lawson Security 10, what is the effect if it is set to "N", vs "Y"? Anyone know?
Okay I just heard back from Infor. Does not matter what it is set to, Y, or N. Same effect either way. Since there is no more LAUA, the flag has no impact at all.
Yes I know how it we use it on LSF9, we are still using LAUA in our production system, and testing security (some folks set to Y and some set to N). Obviously our LSF10 test system has no LAUA and I wanted to ensure that the flag was no longer used, since I have lots of people with it set both ways. So it one thing less to worry about - which is a good thing.
Hmmm....can you guys look at your system account (would start with your env name, would be <env name>_system (e.g LSF10PROD_system) and see what the flag is set to for that account? I was just informed by someone else that these type of accounts always need the flag set to N. And if that is the case, then clearly the flag DOES have an impact.
Yup. Just tried Lapm for HR11, and it came right up. I wonder if this is a difference in our versions. This is 10.0.9.1611 technology.
Well I can't even bring up the Desktop Client, it just spins...and it's been years since I have even tried it. I really have only one, maybe 2 users that would ever use it - I will have to check with one of them next week and see if they can access the LSF10 server that way.
FYI - I found this in Infor support. Archived KB 1542542
"The Desktop Client Logon (frontend32.exe) has been decommissioned as of version LID 10. There is only one LID version per release so LID 10.x will work with both LSF901 and LSF10. In addition LID now also has specific installers for 32-bit and 64-bit environments.
Any installations of the Desktop Client Login may continue to work, but will not be supported."