How Road Rager Added Users

Road Rager has chosen to add users in two phases. First, the assistant security administrator will manually add Resource Management information for all users through the Resource Management Administrator tool. Then the security administrator and the software developer will work together to create files of user credentials in XML format that will be imported in the LDAP server.

Prior to adding any users, however, Road Rager made the smart decision to gather user information ahead of time. They compiled the information in a worksheet.

Step 1: Locate user information

Prior to adding users to the system, the Road Rager security administrators, used a worksheet to gather user information. The information gathered through the worksheet included:

  • Authentication information for all services or agents to which this user needs an identity.

  • OS login information, either for this user or, if the user can be linked to an existing OS user, the existing user's login information.

  • Names of roles that should be assigned to the user.

  • Names of groups that the user belongs to.

Step 2: Add RM Information

Using the Add User Worksheet for reference, the assistant security administrator created user entries in the LDAP server and populated attribute information for such things as:

  • User Name

  • Resource Management ID (ID attribute)

  • Role assignments

  • Group assignments

Step 3: Add identities through XML file import

In conjunction with the software developer, Road Rager's security administrator created an XML file of user identity information for the OS/Environment service and the SSOP services (the only services for which Road Rager users need identities).

Following instructions in the administration document, the Road Rager administrators performed the following basic procedures:

  • Used ssoconfig (the command line tool for configuring the Single Sign-on engine) to create a template for the XML files.

  • Populated the XML files. The Road Rager software developer wrote a program that read the RMID information from Resource Management and operating system information and then wrote the information, along with other user attributes as needed, to an XML file.

  • Imported the identity data to Resource Management.

Note: In reality, Road Rager would most likely not use this method for adding user identities. They have a small enough number of Lawson users to make it practical for them to add identities manually at the same time user entries are added to Resource Management. However, customers with large numbers of users needing identities would want to automate the process in some way.

Make sure database user has required access

A database user is a user that runs the database that contains Lawson data. There are several ways that database users can be configured. Like EZShed did, Road Rager has one user ID that runs the database in background.

The Lawson consultant who installed the system, not Road Rager security administrators, added this user and performed other setup as needed. No other Road Rager users need identities on the database service.

Note: Depending on how customers choose to set up and use their systems, they might need to add user identities to the database service.