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-2313: Enabling "Do not require Kerberos Preauthentication Kerberos Preauthentication" causes adclient to crash

Authentication Service ,  

12 April,16 at 11:11 AM

Applies to: Centrify DirectControl 5.0.5 or below on RedHat 6.2

Problem:

In Active Directory Users and Computers console, Account options "Do not require Kerberos Preauthentication" is checked in user's profile.

User-added image

Attempting to ssh into a RedHat 6.2 server as this user will stall the session and eventually cause adclient to disconnect, following messages can be captured from debug log:
Jan 17 15:34:06 host adclient[2961]: DEBUG <fd:28 PAMVerifyPassword > dns.findkdc KDC locator for domain.com
Jan 17 15:34:52 host sshd[29990]: Invalid user rlevin1 from 123.456.789.123
Jan 17 15:34:52 host cdcwatch[2962]: ERROR cdcwatch detected adclient is not running properly (ping took 30 seconds)
...
Jan 17 15:35:21 host adclient[30042]: DEBUG <fd:27 PAMVerifyPassword > dns.findkdc KDC locator for domain.com
Jan 17 15:40:11 host cdcwatch[30043]: DEBUG lrpc.session New socket 8 (142709)
Jan 17 15:40:41 host cdcwatch[30043]: DEBUG cdcwatch signalling adclient[30042] with SIGABRT

Workaround:

Uncheck "Do not require Kerberos Preauthentication" option in ADUC for target user.

Resolution:

This has been fixed in Centrify DirectControl 5.1.0 and above.

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

Related Articles

 articleKB-8538: After Enabling Smartcard, sctool -s Gives the Error "Cannot determine Centrify Smart Card status" articleKB-5596: User unable to login to User Portal after enabling "User must change password at next logon" in ADUC articleKB-2553: Adding computers to Deployment Manager causes 100% CPU usage articleKB-10410: Recovery key not send back to Active Directory for OS X 10.13.x and Centrify 5.5.x after enabling FileVault articleKB-4669: Starting Centrify agent may cause timed out on Solaris platforms articleKB-5525: Failed to verify account information when enabling provisioning for Box with "SSO required" articleKB-2585: High memory usage when SELinux is enabled/enforced articleKB-3925: How to add Centrify parameter to a group policy articleKB-9255: An application process receives segfault in libnss_centrifyda.so.2 error causing backups to fail