Verify LDAP user attributes (optional)
You must collect data about user attributes if you are doing one of the following:
-
You already have users set up in an LDAP and want Lawson to consume your existing user data. Lawson data can be imported into an existing AD LDS or Directory Server instance. In this scenario, Lawson will use the resource DN location you provide to access your existing LDAP and consume the users you have already set up.
-or-
-
You are installing multiple Environments that will use a single LDAP schema. In this situation, you create a resource DN so that all Environments on your system can share the same resource data. Even though you do not have user data in the LDAP yet, you must tell the install program how you plan to define your users so that the default users created at install time are set up properly.
During the installation of this product, you must supply a value for the structural class that defines users in your LDAP instance.
Structural Class | Definition |
---|---|
inetOrgPerson |
The most common structural class for users in ADAM/AD LDS and Directory Server. If you choose this option, the installation program will assume that your users are set up with the following standard attributes:
If users are set up with different attributes, choose "other" as the structural class. You will be asked to specify the attributes individually. |
user (AD LDS only) |
If the existing LDAP instance is AD LDS, the structural class can be user. If you choose this option, the installation program will assume that your users are set up with the following standard attributes:
If users are set up with different attributes, choose "other" as the structural class. You will be asked to specify the attributes individually. |
other |
Choose other if the following circumstances apply:
|