Adding AgileForms Users from Multiple Active Directory Domains

You can add users to AgileForms from multiple Active Directory domains. The LDAPMultipleDomains configuration setting provides the ability to activate this functionality, and to configure the connection strings for multiple domains.

If this setting is not present, the value is assumed to be "false."

Navigation

  1. In a text editor, open the file [AgileForms Server installation folder]\Webroot\web.config.

Instructions

  1. In the AgileForms web.config file within the <appSettings> node, add the following node:

    <add key="LDAPMultipleDomains" value="[value]" />

    Key Value

    LDAPMultipleDomains

    Definition:
    Specifies whether to use a default LDAP search string, or a list of custom, overriding search strings.
    Allowed Values:
    • True - Indicates that all new users are searched based on a default LDAP search string for the domain identified in their user name.
    • List search strings - Specifies overriding LDAP search strings for one or more Active Directory domains.
    Default Value:
    True
    Example:
    A company has multiple Active Directory domains: MYCORP1, MYCORP2, MYCORP3. The primary domain is MYCORP1.

    When a new user, JSmith, logs on to AgileForms for the first time, the LDAP search for his Active Directory account depends upon the value of LDAPMultipleDomains.

    • True - If LDAPMultipleDomains, is set to True, the user will be searched based on his domain and user name using the connection string LDAP://[DOMAIN]/JSmith. JSmith may be MYCORP1/JSmith, MYCORP2/JSmith, or MYCORP3/JSmith, but as long as JSmith is on the primary server, AgileForms will find his account.

      <add key="LDAPMultipleDomains" value="True" />

    • List search strings - If users in some domains are on specific servers that need to be specified in the LDAP connection string, then you must define those connection strings in the value of LDAPMultipleDomains.

      If MYCORP3 uses the main LDAP server, but MYCORP1 and MYCORP2 use subservers, then the node might look like the following:

      <add key="LDAPMultipleDomains" value="MYCORP1:MYLDAPSERVERA;MYCORP2:MYLDAPSERVERB" />

      In this case, if JSmith were in the MYCORP1 domain (MYCORP1/JSmith), then the LDAP connection string would be LDAP://MYLDAPSERVERA. However, if JSmith were on the MYCORP3 domain, the connection string would be LDAP://MYCORP3.