LDAPSecMgr uses insecure LDAP even when LDAPS specified
Description
Even though the admin configured LDAPS on secure port 636, when the ldap security manager starts up it performs an anonymous bind to LDAP/389 in order to query some DC feature support. Should use the configured connect method
Conclusion
None
Activity
Show:
Russ Whitehead June 20, 2018 at 3:18 PM
This is blocking the Risk Defense Platform (RDP)
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Even though the admin configured LDAPS on secure port 636, when the ldap security manager starts up it performs an anonymous bind to LDAP/389 in order to query some DC feature support. Should use the configured connect method