Make LDAP configrable at the point of installation

AD calls occurs over the LDAP protocol. When an object (user or group) resides in another domain, the domain controller sends a referral back. This means that it sends a pointer and the LDAP client (ISM) is required to contact the referred server to get the object required.

I made a small LDAP client in Powershell (.NET class System.DirectoryServices.DirectorySearcher) to mimic how I believe ISM handles LDAP communication. When I turn off ReferralChasing, I see identical behaviour as Jacobs is having.

When I enable ReferralChasing, I can get at the users and groups in other domains.

My current suspicion is that ISM needs to updated with the following:

• Implement ReferralChasingOption = All
  https://docs.microsoft.com/en-us/dotnet/api/system.directoryservices.referralchasingoption?view=dotnet-plat-ext-6.0#system-directoryservices-referralchasingoption-external

• Remove PageSize if used. If PageSize is set, ReferralChasingOption is omitted.
  https://social.msdn.microsoft.com/Forums/en-US/4f2e4f81-a581-4006-a85f-218cb55a7b8a/systemdirectoryservicesdirectorysearcher-referralchasing-and-pagesize-together?forum=netfxbcl

If we implement this in a fix release, I assume Jacbos would only need to update web.config to point at jacobs.com instead of europe.jacobs.com after installing the fix to resolve the cross-domain issue.

Default value for ReferralChasing is ‘External’ in .NET System.DirectoryServices.DirectorySearcher class which would lead to the issues we’re seeing at Jacbos.

If we can get a test release with ReferralChasingOption = All and PageSizeturned off, I have a multi-AD environment with ISM that we can use to test.

This should be defaulted to "All"