Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.

LDAP integration via MID Server

Log in to subscribe to topics and get notified when content changes.

LDAP integration via MID Server

Administrators can integrate using an LDAP data source over a Management, Instrumentation, and Discovery (MID) Server.

The MID Server facilitates communication and movement of data between the platform and external applications, data sources, and services. For details on installing a MID Server, see MID Server installationMID Server installation.

You can use the MID Server to import data over LDAP, but you cannot use the MID Server for LDAP authentication. A MID Server does not support SSL connections.

Using a MID Server to establish an LDAP connection prevents you from having to expose the LDAP server to external network traffic. It also eliminates the need to establish a VPN tunnel between your LDAP server and data centers.
Note:
  • The MID Server user must have the user_admin role in order to be able to read LDAP server configuration records.
  • The following are not available with the MID Server:
    • LDAP authentication
    • SSL connection
    • Refreshing user and group records from LDAP

A MID Server connection communicates over HTTP on port 80 by default. This communication channel does not require a certificate. The connection between the MID Server and the instance is over HTTPS (port 443).

An instance can connect to an LDAP server via the MID Server. When you do this, the instance communicates with the MID Server via HTTPS, and the MID Server communicates with the LDAP server via LDAP (port 389). The instance can also connect to the LDAP server directly, using LDAP or LDAPS, either over the internet or through a VPN tunnel.

Note: LDAP cannot communicate via the MID Server with password authentication.

To set connection properties for a specific LDAP server, see Define an LDAP server.

Feedback