LDAP Integration

Creating an LDAP Source Definition

 

The LDAP Integration feature enables an agent that updates and synchronizes iSupport Customer Profile, Support Representative Profile, and Asset records with the information in one or more LDAP sources.

You’ll  use the Data Source Integration screen to create a data source integration definition to specify the server and related settings, field mappings, and exclusions, and use sync definitions to specify the type of record you are synchronizing and the directory node and filters for the data to be synchronized. You can utilize both filtering and exclusions to specify the values that should not be synchronized; what you use will depend on how much you need to prevent from synchronizing for the level in the targeted source. You can also set default values based upon the LDAP sync setting entry from which a record was created. Exclusions target everything under a node in a directory and apply to all sync definitions of the same record type within a data source integration definition. Filters use syntax that can target multiple nodes in a tree, and apply to a specified base directory node in a sync definition.

The following occurs when the agent runs:

If a Windows login name exists in the LDAP record, it will be included in the mySupport User Name field for authentication to the mySupport portal. You’ll need to disable LDAP integration in order to enter or change the password for accessing the mySupport portal. The password will not be changed by re-enabling LDAP integration.

The initial synchronization process will populate the Secondary User Name field if the iSupport Services user account is a domain level user account. For ease of entry, it is approximated by retrieving the text between the @ symbol and the next period from the user’s principal name and converting it to upper case (for example, LBLSOFT would be retrieved from [email protected]) and adding a backslash, and then retrieving the username portion from the samAccountName field of an LDAP user entry.

Because this login may be different if there are multiple domains, this field will be editable and will not be synchronized again after the initial synchronization. If your environment consists of multiple domains, you’ll need to verify that the approximated Secondary User Name entry is correct.

When the feature is enabled, the agent runs immediately and then on an interval basis according to the selection in the LDAP Synchronization field. The LDAP Integration feature does not modify the contents in the LDAP source in any way.

Go to the following links for more information: