This article covers setting up "Secure" Active Directory connection, LDAP over SSL (LDAPS) and LDAP signing. The lab was setup with Security Options > Domaincontroller: LDAP server signing requirements & Network security: LDAP server signing requirements as Require signing. Microsoft is releasing an update (LDAP channel binding and LDAP signing) to increase security with communication between LDAP clients and Active Directory domain controllers.
Spider supports LDAPS and LDAP signing polices.
The default port for LDAP is port 389, but LDAPS uses port 636 and establishes SSL/TLS upon connecting with a client.
For initial setup, please refer to the User Manual section 8.5.1 for setting up Active Directory.
The document will be revised for LDAP channel binding.
Please follow these steps.
Set domain policy up for LDAP Server signing requirements.
Log on Spider as the Administrator into the Default (0) Mandator.
Open System and then Active Directories.
Open Default Mandator.
In the Top Level parameter the standard will be set to your domain settings such as "LDAP://domain.corp" to enable LDAPS, adjust the parameter to "LDAP://domain.corp:636".
Restart the Spider Core Service.
The Windows authentication login will log on using LDAPS.
For assistance or questions. Please contact Flexera Support.
Mar 02, 202009:47 AM - edited Feb 08, 202103:37 AM