Question: Does Centrify DirectControl support LDAP over SSL (LDAPS)?
Answer: Support for LDAPS over port 636 (server authenticated and encrypted) is not supported by Centrify.
DirectControl authenticates and encrypts all communications with Active Directory using Kerberos (GSSAPI) resulting in an already secured LDAP connection.
Although DirectControl communicates with Active Directory over the standard LDAP port 389, each machine must authenticate to Active Directory before it can establish (GSSAPI) connection. After connection is established, all traffic through this connection is encrypted with this uniquely negotiated key. This can be referred to as a "signed and sealed" connection.
This is managed with the following Windows Group Policies:
The Group Policies are located here: Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options:
"Domain controller: LDAP server signing requirements" set to Require signing.
"Domain member: Digitally encrypt or sign secure channel data (always)" set to Enabled.
The network trace would show the indisputable evidence; Centrify LDAP traffic are set for GSSAPI Privacy. One exception is LDAP Ping which use UDP but there is no sensitive information in LDAP Ping and allowed by Microsoft.
LDAP over SSL on port 636 is a certificate-based method of encryption (thus introducing additional dependencies on certification) instead of kerberos session-key-based. This would be a very fundamental change to the product and so is unsupported by Centrify.