We are deploying a LD ServiceDesk Suite 7.6.1 test environment.
We would like to import the analyst and the end-users from the AD to use it later for integrated login.
We have created the data connections and the data types (one for Analysts and one for End-users, based on a LDAP filter which queries AD "Analyst" group membership. We have setup a coupe of queries to verify that the data types import the required fields.
We have some confusion while configuring the data mappings.
Here is what we do for the End-Users:
We choose the OurAD data connection as Source Module and the OurEndUser data type as the Business Object.
We choose System as the Target Module and End User as the target BO. (Should we select here User?? Or maybe any other such as User Network Login?? Can someone explain the difference/reason/criteria to choose one or another??)
The mapping that we do is as follows (first level is the LDSDS target attribute, and below indented the AD source attribute/s):
Address, Country-Name, Text-Country, Postal-Code, Locality-Name
We assign Name as the Target Key Attribute, as the UPN is unique in the AD.
We also assign default values for the current and primary groups. Here we get an error telling that "Full Name" and "Login ID" are mandatory and require population. (Is this normal? How can I assign the Login ID? I would like that the Login ID is also the User-Principal-Name but there is not such an attribute anywhere... how can I specify that?)
To implement the integrated login later, should we do any mapping to the Network login? Can someone explain us how to do this?
Does the mapping that we do make sense? We have tried to find in the forums and documentation hints on how to map the fields or how to setup the import from end to end, but we have found nothing clear.
Thank you very much in advance!