Set up a connection to on-premise Microsoft Active Directory

Name •

Name the connection. Be sure to provide a clear and distinguishable Name as soon as the connection is created. Throughout integrator.io imports and exports, you will have the option to choose this new connection, and a unique identifier will prove helpful later when selecting among a list of connections that you’ve created.

Agent •

Select an agent from the list that you have created inside integrator.io. If you have not yet created an agent, see Integrate data through firewall with on-premise agent . To connect to an on-premise application, integrator.io requires that you install an agent on a networked computer. An agent is a small application that allows you to connect to data behind your firewall. When installing an agent, you will specify a unique access token, which then populates the Agent drop-down list. The installed agents connect to integrator.io and establish a reverse SSH tunnel that allows secure communication without the need to whitelist integrator.io’s IP addresses in your firewall settings. Multiple connections can use the same agent.

Host •

The host name or IP address of the Active Directory server.

Port •

By default, the TCP/UDP port 389 is enabled on Active Directory. When SSL is required, select the Use SSL check box and use the SSL/TLS-protected port 636. (SSL establishes a secure connection to the database. Using this option ensures that data in transit is encrypted.)

Base DN •

The base portion of the distinguished name, that is, the object or the point from which the server will start the user lookup. Specifying a base DN may greatly improve performance when returning entries for large servers by limiting the number of entries that need to be examined.

See also, Distinguished Names in Microsoft documentation.

Username •

Enter the user name to authenticate to the Active Directory server.

Password •

Enter the password to authenticate to the Active Directory server.

LDAP version •

Select the LDAP version used to connect to and communicate with the server.

Configure properties

Define additional configurations for the database connection. For example, you can configure the connection timeout if the server you are trying to connect to is slow.

Borrow concurrency from

Select another connection from the list. By default, all data flowing through a connection record is submitted to the respective endpoint application at the Concurrency level configured for that connection record. There are cases, however, where multiple integrator.io connections need to share the same concurrency level, and this field allows you to specify which connection you would like to borrow from. With borrowed concurrency, the data flowing through both connections will be submitted to the endpoint application together, via a shared concurrency model.

Concurrency level

Set this field to limit the number of concurrent HTTP requests (up to 25) allowed by the connection resource at any one time, or leave this field blank to use burst mode. With burst mode, integrator.io will make HTTP requests as fast as possible, with high levels of concurrency.

Configure encrypted fields

Store all sensitive fields required by your imports and exports to access the app you are connecting to. Click the Expand window (

) button to modify the JSON sent to the app in the Encrypted Advanced Field Editor . For example, enter {"secretKey": "someSecretKeyValue"} . (You can also retrieve these sensitive values elsewhere, such as How to test this connection? , via the example handlebars format {{{connection.http.encrypted.secretKey}}} .) Multiple layers of protection are in place, including AES 256 encryption, to keep your connection’s encrypted fields safe. When editing this form later, you must enter this value again; it is stored only when the connection is saved and never displayed as text.