---
sourceDocument: Australia Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-security

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# LDAP integration setup

# LDAP integration setup {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Administrators can enable LDAP integration to allow sign-on of users from their company
LDAP directory.
LDAP typically uses one of these types of communication channels.  
{#c_LDAPIntegrationSetup__table_LDAPCommunicationChannels__entry__4}

| Connection | Description | LDAP import support? | LDAP authentication support? |
|-|-|:-:|:-:|
| 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). You can use the MID Server to import data over LDAP, but you cannot use the MID Server for LDAP authentication. Proceed to [Define the LDAP Server](https://www.servicenow.com/docs/JJdkpBibwnesJEgF8SZRoA "Create a new LDAP server record in the instance."). | Yes | No |
| Standard LDAP integration | Communicates over TCP on port 389 by default. This communication channel does not require a certificate. Proceed to [Define the LDAP Server](https://www.servicenow.com/docs/JJdkpBibwnesJEgF8SZRoA "Create a new LDAP server record in the instance."). | Yes | Yes |
| SSL-encrypted LDAP integration (LDAPS) | Communicates over TCP on port 636 by default, This communication channel requires a certificate. Proceed to [Install the LDAP X.509 SSL certificate](https://www.servicenow.com/docs/44ASm4rr38ougPwu8tBuBw "You can install an X.509 certificate for your LDAP integration.") to obtain and upload the certificate. | Yes | Yes |
| VPN connection | Communicates over an IPSEC tunnel. Purchase or create an IPSEC tunnel on your local network. Proceed to [Define the LDAP Server](https://www.servicenow.com/docs/JJdkpBibwnesJEgF8SZRoA "Create a new LDAP server record in the instance."). | Yes | Yes |
[Table 1. LDAP communication channels]

{#c_LDAPIntegrationSetup__table_LDAPCommunicationChannels} If using a MID Server, the MID Server connects to the instance and the MID Server also connects to the LDAP server. In both cases, the MID Server initiates the connection:

1. First, the MID Server connects to the LDAP server via LDAP on Port 389.
2. Then, the MID Server initiates an HTTPS encrypted connection to the instance on Port 443 to push the data to the instance.
{#c_LDAPIntegrationSetup__ol_pws_xj1_rs}

For more information about VPNs, Mid Servers, and LDAP, see [You Don't Need A VPN Part II](https://community.servicenow.com/community?id=community_blog&sys_id=10dd26e9dbd0dbc01dcaf3231f9619c8&view_source=searchResult) on the community.