Lawson Security

Implementing Lawson Security is a relatively simple and straightforward procedure. If you are planning on taking on this challenge in-house we encourage you to follow the following steps:

1. Spend time on gathering your requirements. This is by far the most important step of the process and you should have a good working document to begin with. If you need templates to start with, feel free to use our templates.
2. Come up with a really great naming convention up front. This will save you all kinds of headaches in the long run. I like to add the word “Role” to all my roles, and “CLS” to all my classes, because later it makes them easier to read and understand as I’m trying to debug. You can come up with your own ideas but keep them consistent.
3. Make sure you have a good backup process for your LDAP data and you have tested it. There is nothing worse than losing your entire implementation because of corrupt LDAP instances. It happens more than you know.
4. Rome wasn’t built in a day. Don’t try to implement all the wishlist of every department in the first phase. Give them the necessities. After they have tested and accepted them, then move on to the fancier stuff.
5. Ask us for a 30-day trial of LSF_IQ when you’re ready to implement because I can assure you that it will save you hundreds of hours of work.
6. Clear all your cache when testing. I’m talking all your cache including:
   1. IOSCacheRefresh
   2. Browser Cache
   3. Security Cache
7. Have a small group of testers. This will ensure that testing is completed in a reasonable time. Otherwise you will be chasing after users for their issues.
8. Create a Google Spreadsheet for issue tracking unless you have a better tool.
9. Roll out to one small group of users at a time. Remember, until check_ls is set to YES, users can still use LAUA

Last but not least, go to the education page on this site and look for webinars related to Lawson Security. There are several there that go over concepts.