Create Additional LoginSchemes for each LDAP in the trust

After you have updated the LoginScheme element of the THICKCLIENT service, you must replicate it on each LDAP server that you want to bind to.

Each LoginScheme element of the THICKCLIENT service represents a corporate LDAP server. For example, if you intend to bind to three LDAP servers, the THICKCLIENT service should also have three LoginScheme attributes one of which is the default login scheme. Make sure you populate the LoginSchemeName attribute with the correct unique name.

For each THICKCLIENT service on each LDAP server, update its XML file with the following Attribute Name and Description pairs:

  • PROVIDER: LDAP Provider URL to access

  • LOGIN_RDN Root DN or the search base DN of the user tree

  • STRUCTURAL_OBJECTCLASS The user objectclass in your LDAP

  • LOGINSCHEMENAME The name for the loginscheme. Each LOGINSCHEMENAME must be unique, for example, LOGINSCHEME_LDAP2, LOGINSCHEME_LDAP3 and so on.