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-16344: Cenroll failed to enroll host to PAS on-site

Privileged Access Service ,  

25 June,19 at 01:49 PM

Problem:

Cenroll failed with error:

"Failed to initialize connection to Centrify identity platform: Failed to connect to Centrify identity platform"

 
Cause:

SHA512 was used on TLS 1.2 on the environment.  The maximum supported algorithm is SHA384 for TLS 1.2 according to Microsoft.

In event viewer, the following error message may be seen: 
 
An TLS 1.2 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The SSL connection request has failed. 

 
Windows_Event_TLS_Cipher_Unsupported.png

Reference:
https://blogs.technet.microsoft.com/silvana/2014/03/14/schannel-errors-on-scom-agent/
 
Solution:

SHA512 is not supported on TLS 1.2. After reconfiguring the Certificate Authority to use SHA256 and cenroll works successfully.
 

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

Related Articles

 articleCentrify 19.4 Release Notes articleCentrify 20.1 Release Notes articleKB-16163:Fail to cenroll when machine is added to PAS portal by Discovery articleCentrify 17.1, 17.1 Hotfix 1 & Hotfix 2 Release Notes articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS articleCentrify 18.2 Release Notes articleCentrify 17.4 and 17.4 Hotfix Release Notes articleCentrify 18.3 Release Notes articleCentrify 17.6 and 17.6 Hotfix Release Notes