Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-7922: What Potential Issues Might Arise if SSLv3 is Disabled After Installing CPS?

Privileged Access Service ,  

22 December,16 at 12:28 AM

Applies to: All versions of Centrify Privileged Service

Question:
What Potential Issues Might Arise if SSLv3 is Disabled After Installing CPS?

Answer:
SSLv3 is known to be susceptible to attacks such as POODLE. CPS on Premise only requires TLSv1 and higher to work, so we can disable SSLv3 as a matter of caution by setting the below registry key to 0.

HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server\Enabled



 

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6044: How to configure users for automatic Kerberos Credentials for infinite renewal even after users have logged out? articleKB-6050: How to configure a group for automatic Kerberos Credentials for infinite renewal? articleKB-8172: Error installing sql express with Reporting Services Wizard articleKB-6745: CPS auto login fails using stock Solaris sshd articleKB-6041: How to show current license type in use by adclient articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-4116: Unable to perform DA install if NT Authority\system account is unavailable