Setup
...
LDAP
How to enable LDAPS (LDAP over SSL)
2 min
description ldaps is a mechanism for connecting to ldap servers over ssl while ldaps can be enabled for activate it has no benefit ldaps is primarily used for non microsoft clients ldaps is best used to protect credentials during a simple ldap bind this is when a user name and password could be exposed there is no real need or use for ldaps in any other scenario, but using non microsoft clients, and some third party applications that do not have their own secure method of communicating with dcs, and that do not rely on the built in microsoft apis most microsoft based clients don’t need to use ldaps for example, mmc snap ins use sign and seal, which means that they use integrated authentication that is encrypted; for many apps, the ldap traffic itself is sealed via kerberos or ntlm the active directory domain service administration tools still use port 389, but they are protected by the sign and seal binding activate uses exactly the same mechanism to secure communications between the activate server and active directory, however, some customers have asked to enable ldaps anyway solution if the following conditions are true then ldaps can be enabled on your activate server by setting the following value and restarting all services //resources/activedirectory/ldapusessl = true conditions this is a server wide setting therefore all ldap servers (ie all dc's in all forests) must have valid certificates and have ldaps enabled the certificate must be valid and trusted by the activate server ldaps should be extensively tested in the environment before enabling on your activate server ldaps uses different ports and must be available through any intervening firewalls activate support does not cover debugging ldaps issues