Regarding LDAP integration and other Rest and SOAP intgrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2017 10:05 PM
Is there any Free site or instance which holds LDAP server so that we practice LDAP integration with SNOW . I mean to say test servers (LDAP).
What is about github.com is it useful for practicing integrations of SNOW.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2017 10:11 PM
Hello Ratnaker,
You can use below link for testing the credentials LDAP:
Online LDAP Test Server - Forum Systems
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2017 10:38 PM
Hi Surya,
Can we use this test server to Integrate LDAP with SNOW. What about the site Github.com I didn't have much information about this . I saw this site details in one of the Servicenow videos.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2017 10:20 PM
if you want to learn about ldap integration then you can check the servicenow wiki. they used test mid server.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2017 10:56 PM
Hi Karne,
An LDAP integration allows your instance to use your existing LDAP server as the master source of user data.
The integration uses a read-only connection that never writes to the LDAP directory. The integration only queries for information, and then updates its internal database accordingly.
Administrators can enable an LDAP integration to allow single sign-on of ServiceNow users from their company LDAP directory.
After the integration, 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:
- The MID Server connects to the LDAP server via LDAP on Port 389.
- Then the MID Server initiates an HTTPS encrypted connection to the instance on Port 443 to push the data to the instance.
LDAP typically uses one of these types of communication channels:
- 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). You can use the MID Server to import data over LDAP, but you cannot use the MID Server for LDAP authentication.
- A standard LDAP integration communicates over TCP on port 389 by default. This communication channel does not require a certificate.
- An SSL-encrypted LDAP integration (LDAPS) communicates over TCP on port 636 by default, This communication channel requires a certificate.
- A VPN connection communicates over an IPSEC tunnel. Purchase or create an IPSEC tunnel on your local network.
- A MID server initiates one connection to an LDAP server via port 398, then initiates an encrypted HTTPS connection to an instance via port 443 to push data to the instance.
For more information, try this, "Getting Started with LDAP Integration"
To set up LDAP integration via MID Server,
- 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
Please Note:
- Whenever you consider importing any data into your Service-now instance, only import the information that is actually necessary within the tool.
- To prevent unnecessary data from coming into your system add a comma-separated list of attributes to be brought over from your LDAP server to the LDAP Server record in your instance.
- To completely minimize the amount of data brought over, this list should contain only those fields used in your transform map.
Lastly, I bumped across a video that might help you for your reference.