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-1863: KDC refused skey: Client not found in Kerberos database

Centrify DirectAudit ,   Centrify DirectControl ,   Centrify Identity Service, Mac Edition ,  

12 April,16 at 11:02 AM

Applies to: All versions of Centrify DirectControl.

Problem:
Centrify is disconnected when the command adinfo -V is issued. Re-starting is not helping either. From the debug log, the following messages are seen

"KDC refused skey: Client not found in Kerberos database". 

Cause:
This is not a common occurrence but can happen when there is a corruption in Kerberos config files.

Workaround:
The following commands needs to be executed as root in the following order:

1. Login the host as root 
2. Run: adleave -f  (-f means force as its in disconnected mode & adleave will not work)
3. Run: rm /etc/krb5/krb5.conf (or /etc/krb5.conf)
4. Run: rm /etc/krb5/krb5.keytab  (or /etc/krb5.keytab)
5. Run: rm etc/krb5/krb5.ccache (or /etc/krb5.ccache)
6. Run: adinfo --diag <DOMAINNAME> (This can be skipped if all ports for the domain controllers are opened). 

7. Join the host to domain by using the adjoin command. 

If there is still any problem, please help support to collect the log files:
KB-0062: How to Collect Debug Logs from a DirectControl Agent

Resolution:

Future releases of software will take steps to minimize corruption in Kerberos files.

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