Adding Users to a CloudSuite Deployment
Adding Users to a CloudSuite Deployment Step 1: Populating a CSV File of User Data
Infor CloudSuite user data is added through a CSV file created by the customer-administrator. The file is read by a script developed by Infor and accurate data in the CSV file is critical to a successful upload of user data. This document describes the columns of the CSV file. The Add User service request page provides a sample CSV file.
CSV file creation tools and formatting
Infor strongly recommends using Microsoft Excel or an equivalent spreadsheet tool to create and edit the CSV file. Automated CSV-file-generation tools can also be used as long as CSV standards are met. Do not use quotation marks of any kind for data in any column, because Excel (or any other spreadsheet tool) manages them for you. Do not use a simple text editor to create the CSV file. This is because the possibility of creating a file with errors is very high when using a simple text editing tool.
CSV file column descriptions
The table describes the columns of the CSV file and provides details about how to populate them.
Column Name (Attribute)
Description
Ssop (Required if LSfLevel is set to Yes)
If your INFORBC deployment is configured as an ADFS Trust relationship with your domain, specify SSOP identities in the format: YourDomain\User11
UserName (Required)
Unique ID of the user. This ID identifies the user throughout the CloudSuite system. This data is used for the RMID field and the LSENV identity. The maximum field length is 80 characters; no special characters are allowed.
If your INFORBC deployment is standalone (that is, you have not yet configured ADFS), specify SSOP identities in the format: [email protected]
ThickclientAdUpn
No special characters (for example, * _ @) are allowed.
This field is required only if the THICKCLIENTLDAPLS is defined. This is the User Principal Name from your company's Active Directory specific to the user's record. Example: [email protected]
1
continued from previous page
Column Name (Attribute)
Description
FirstName (Required)
First name of the user. This attribute can be up to 15 characters and can include spaces.
LastName (Required)
Last name of the user. This attribute can be up to 25 characters and can include spaces.
Email (Required)
Email address of the user.
Groups
Productline JobQueueAccess Addins Oledb PortalAdmin Workflow Requester Employee EmployeeCompany PortalRole
The group or groups that the user is being assigned to. Use only valid, existing groups. Separate groups by commas, for example, GROUP1,GROUP2,GROUP3 Note: If you are not using Excel or an equivalent spreadsheet tool you must enclose the list of groups in double quote marks (“GROUP1,GROUP2,GROUP3”) and make sure that there are no spaces before or after commas.
The set of applications and data that this user will use and must be in all capital letters, for example, LSAPPS. Gives the user access to job queues. Enter "Y" or "N."
If the user is allowed to use Infor Lawson Addins for Microsoft (Addins), specify Y; if they are not allowed to use Addins, use N. If the user is allowed to use the OLE DB Object Connector (OLEDB) product, specify Y; if they are not allowed to use OLEDB, use N.
If the user will be an administrator of the Lawson for Infor Ming.le interface, use Yes; if not, type No.
If the user is allowed to use Infor Process Automation, type 1; if not, user 0.
ID on the Requestor Self Service application, if used. Used for the LSAPPS_REQUESTER identity. ID on the Employee Self Service application, if used. Used for the LSAPPS_EMPLOYEE identity.
The name of the company that this ESS user is assigned to. Used for the LSAPPS_EMPLOYEE identity.
If you use "Portal" roles, that is, roles that define what users see in their Lawson for Infor Ming.le portals, populate this column with the name of the XML file that contains the role. (Typically, this is default.xml.) 2
continued from previous page
Column Name (Attribute)
Description
ADLevel (Required)
Specifying Yes here creates the INFORBC AD user. Note If LsfLevel is also Yes then the INFORBC AD user will be created and the lsenv identity will be populated. The lsenv identity is needed for batch and LID users.
Roles
The security role or roles that the user has been assigned to. These roles determine the access to applications and data that a user has. Use only valid, existing roles. Separate roles by commas, for example, ROLE1,ROLE2,ROLE3 Note: If you are not using Excel or an equivalent spreadsheet tool you must enclose the list of groups in double quote marks (“ROLE1,ROLE2,ROLE3”) and make sure that there are no spaces before or after commas.
Specify No here if you do not need to create this user. You might choose No here if, for example, a record for this user is already on Infor BC AD or if the record is for a Self-Service user.
LsfLevel (Required)
For No-Trust configurations, the ADLevel is ignored and the user is always added or, if the user already exists, then the password is reset. For Trust configurations, the ADLevel value is checked. Specifying Yes here adds the user to LSF and kicks off the list-based sync in ISS. (This sync updates the user in both ISS and Landmark). Specify No here if you do not need to create this user. You might choose No here if, for example, a record for this user is already exists on LSF.
3
Step 2: Creating and Submitting the Add Users Service Request
1. Navigate to your CloudSuite customer administration main page and, from the topleft corner, select the Service Request tab and then click Create a New Service request in the upper-right corner of the screen.
2. From the Service Request Wizard dialog box, select the deployment that you want to update and then select the Service Request type, in this case, Add users. Click Next.
3. From the Add Users dialog box, type or make selections for the following: Single Sign-on Enabled (ADFS)?: Select YES if the ADFS trust for your installation has already been set up. Select NO if has not been. Upload a CSV File: Select the CSV file that contains the user data. Force Password Reset: Select YES if you want any existing passwords for users to become void. The system sends an email for password reset to all users in the input file. Select NO if you want passwords to be generated for all users in the input file. The generated passwords are included in the Passwords file as output contained in the Service Request Details.
4. Click Save.
5. Watch for the information messages that your CSV file has been successfully uploaded and the Service Request has been submitted. These messages appear on the upper-right of the screen. 4
Infor CloudSuite user data is added through a CSV file created by the customer-administrator. The file is read by a script developed by Infor and accurate data in the CSV file is critical to a successful upload of user data. This document describes the columns of the CSV file. The Add User service request page provides a sample CSV file.
CSV file creation tools and formatting
Infor strongly recommends using Microsoft Excel or an equivalent spreadsheet tool to create and edit the CSV file. Automated CSV-file-generation tools can also be used as long as CSV standards are met. Do not use quotation marks of any kind for data in any column, because Excel (or any other spreadsheet tool) manages them for you. Do not use a simple text editor to create the CSV file. This is because the possibility of creating a file with errors is very high when using a simple text editing tool.
CSV file column descriptions
The table describes the columns of the CSV file and provides details about how to populate them.
Column Name (Attribute)
Description
Ssop (Required if LSfLevel is set to Yes)
If your INFORBC deployment is configured as an ADFS Trust relationship with your domain, specify SSOP identities in the format: YourDomain\User11
UserName (Required)
Unique ID of the user. This ID identifies the user throughout the CloudSuite system. This data is used for the RMID field and the LSENV identity. The maximum field length is 80 characters; no special characters are allowed.
If your INFORBC deployment is standalone (that is, you have not yet configured ADFS), specify SSOP identities in the format: [email protected]
ThickclientAdUpn
No special characters (for example, * _ @) are allowed.
This field is required only if the THICKCLIENTLDAPLS is defined. This is the User Principal Name from your company's Active Directory specific to the user's record. Example: [email protected]
1
continued from previous page
Column Name (Attribute)
Description
FirstName (Required)
First name of the user. This attribute can be up to 15 characters and can include spaces.
LastName (Required)
Last name of the user. This attribute can be up to 25 characters and can include spaces.
Email (Required)
Email address of the user.
Groups
Productline JobQueueAccess Addins Oledb PortalAdmin Workflow Requester Employee EmployeeCompany PortalRole
The group or groups that the user is being assigned to. Use only valid, existing groups. Separate groups by commas, for example, GROUP1,GROUP2,GROUP3 Note: If you are not using Excel or an equivalent spreadsheet tool you must enclose the list of groups in double quote marks (“GROUP1,GROUP2,GROUP3”) and make sure that there are no spaces before or after commas.
The set of applications and data that this user will use and must be in all capital letters, for example, LSAPPS. Gives the user access to job queues. Enter "Y" or "N."
If the user is allowed to use Infor Lawson Addins for Microsoft (Addins), specify Y; if they are not allowed to use Addins, use N. If the user is allowed to use the OLE DB Object Connector (OLEDB) product, specify Y; if they are not allowed to use OLEDB, use N.
If the user will be an administrator of the Lawson for Infor Ming.le interface, use Yes; if not, type No.
If the user is allowed to use Infor Process Automation, type 1; if not, user 0.
ID on the Requestor Self Service application, if used. Used for the LSAPPS_REQUESTER identity. ID on the Employee Self Service application, if used. Used for the LSAPPS_EMPLOYEE identity.
The name of the company that this ESS user is assigned to. Used for the LSAPPS_EMPLOYEE identity.
If you use "Portal" roles, that is, roles that define what users see in their Lawson for Infor Ming.le portals, populate this column with the name of the XML file that contains the role. (Typically, this is default.xml.) 2
continued from previous page
Column Name (Attribute)
Description
ADLevel (Required)
Specifying Yes here creates the INFORBC AD user. Note If LsfLevel is also Yes then the INFORBC AD user will be created and the lsenv identity will be populated. The lsenv identity is needed for batch and LID users.
Roles
The security role or roles that the user has been assigned to. These roles determine the access to applications and data that a user has. Use only valid, existing roles. Separate roles by commas, for example, ROLE1,ROLE2,ROLE3 Note: If you are not using Excel or an equivalent spreadsheet tool you must enclose the list of groups in double quote marks (“ROLE1,ROLE2,ROLE3”) and make sure that there are no spaces before or after commas.
Specify No here if you do not need to create this user. You might choose No here if, for example, a record for this user is already on Infor BC AD or if the record is for a Self-Service user.
LsfLevel (Required)
For No-Trust configurations, the ADLevel is ignored and the user is always added or, if the user already exists, then the password is reset. For Trust configurations, the ADLevel value is checked. Specifying Yes here adds the user to LSF and kicks off the list-based sync in ISS. (This sync updates the user in both ISS and Landmark). Specify No here if you do not need to create this user. You might choose No here if, for example, a record for this user is already exists on LSF.
3
Step 2: Creating and Submitting the Add Users Service Request
1. Navigate to your CloudSuite customer administration main page and, from the topleft corner, select the Service Request tab and then click Create a New Service request in the upper-right corner of the screen.
2. From the Service Request Wizard dialog box, select the deployment that you want to update and then select the Service Request type, in this case, Add users. Click Next.
3. From the Add Users dialog box, type or make selections for the following: Single Sign-on Enabled (ADFS)?: Select YES if the ADFS trust for your installation has already been set up. Select NO if has not been. Upload a CSV File: Select the CSV file that contains the user data. Force Password Reset: Select YES if you want any existing passwords for users to become void. The system sends an email for password reset to all users in the input file. Select NO if you want passwords to be generated for all users in the input file. The generated passwords are included in the Passwords file as output contained in the Service Request Details.
4. Click Save.
5. Watch for the information messages that your CSV file has been successfully uploaded and the Service Request has been submitted. These messages appear on the upper-right of the screen. 4
