Centrify DirectControl version 5.1.3 on all platformsProblem:
Add capability to openldap and adclient to negotiate integrity only security levelCause:Currently Centrify support 3 openldap security level:
- Disabled - no encryption, no integrity check.
- Allowed - depends on what server support, we will use it. If server support encryption & integrity, we use both.
- Required - require signing and encryption, if server does not support it, do not connect to this server.
This makes debugging difficult on the field. If customer environment has signing require GP setting turn on, 'Disabled' option will not work; and there is no way that Centrify can capture unencrypted ldap packet trace with the above 3 settings.
In the new release Suite 2016, Centrify introduce the following parameter in /etc/centrifydc/centrifydc.conf:
The parameter value must be one of the following valid options:
- Allowed - to allow both encrypted and unencrypted LDAP traffic.
- Disabled - to prevent encrypted LDAP traffic.
- SignOnly - to require all LDAP traffic to be signed to ensure packet integrity, but not encrypted.
- Required - to require all LDAP traffic to be signed and encrypted.
If the server does not support encryption and the above setting is set, server connection will be refused.
This is a new security level added in this release. When it is set, adclient negotiates LDAP signing only (integrity only). This configuration parameter specifies the LDAP encryption policy use.
- If an organization has a security policy that does not allow unencrypted LDAP traffic, it is recommended to
use this parameter to specify that all connections to Active Directory are encrypted.
- If an organization is not concern with the encryption of LDAP data and prefer better performance, force all connections to be unencrypted.
If this parameter is not defined in the configuration file, its default value is 'Allowed