Converting from LAUA Security to Lawson Security in the 9.0.1.x Environment

If you use LAUA security for any of your users in your 9.0.1.x environment, you must create equivalent security access for them in Lawson Security before you upgrade to the 10.0.x environment. If you use Lawson Security for some of your users in your 9.0.1.x environment, some of these steps will already be done.

Note: Check the download page for Lawson Security for a tool that can aid in converting LAUA security to Lawson Security. Also, see the LAUA Security Data to Lawson Security Migration Guide.

For full details on setting up Lawson Security, see Lawson Administration: Resources and Security.

To convert from LAUA security to Lawson Security in the 9.0.1.x Environment

  1. Analyze your LAUA security in order to identify the access needs of the users currently controlled by LAUA security. After the 10.0.x Environment is live, you will not have access to the LAUA utility or LAUA reports in the 9.0.1.x Environment.
  2. Create a profile in the Lawson Security Administrator for your application product line. Note that you can create a profile that is not active, thus allowing you to create new security classes and rules without them affecting the running environment.
  3. Create security classes within that profile that correspond to appropriate subsets of rules that users will need.
  4. Create the access rules for each security class.
  5. Create roles and assign the appropriate security classes to these roles.
  6. If SSOP identities do not exist for the users, create them in the User Maintenance component of the Lawson Security Administrator.
  7. On the RM Information screen in User Maintenance, assign one or more roles to the user.
  8. If you want to switch a user to Lawson Security at this time and remove them from LAUA security, set the checkLS field on the RM Information screen to Yes for the user. When you upgrade to 10.0.x, the system will treat this field as set to Yes in all cases.