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-1878: Client not found in Kerberos database while getting initial credentials

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

12 April,16 at 11:37 AM

Applies to: All versions of Centrify DirectControl.

Question:
After SSHing to a Centrify server using AD credentials, the following message appears when using the command kinit. This appears to be a problem with mapping the unix name to the AD display name. In this example: The unix login name is bsmith and the domain account is just smith. If kinit <AD domain user name> is issued, it works as expected. Any reason?

"Client not found in Kerberos database while getting initial credentials"

Answer:
By default, Kerberos tools like kinit obtains and caches an initial ticket-granting ticket for the principal name i.e., AD username. The unix name is only known to Centrify DirectControl. When you run kinit, none of it flows through Centrify DirectControl, instead it goes through Kerberos library which in turn contacts the DC to authenticate the user and get the Kerberos ticket. So you'll have to always specify AD username and not the unix name. 

In the below example, smith is the AD username which will work fine while bsmith is the unix username which will not work as explained above.

-bash-3.00$ klist

Ticket cache: FILE:/tmp/krb5cc_10063
Default principal: smith@yourdomain.com
Valid starting                Expires                Service principal
09/14/10 13:12:13  09/14/10 23:12:13  krbtgt/yourdomain.com@yourdomain.com
        renew until 09/21/10 13:12:13
-bash-3.00$ kinit smith
Password for smith@yourdomain.com:
-bash-3.00$ kinit bsmith
kinit(v5): Client not found in Kerberos database while getting initial credentials 
-bash-3.00$

Additional notes:
For more info, please check the below link on how kinit works. This link is from MIT's website and our code is based on MIT as well.
http://web.mit.edu/kerberos/krb5-1.5/krb5-1.5.4/doc/krb5-user/Obtaining-Tickets-with-kinit.html
 

Centrify Corporation does not take any responsibility for the content or availability of this link and it was provided as a courtesy.  Customers should contact the vendor if there are any further questions

 

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

Related Articles

 articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6041: How to show current license type in use by adclient? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-2962: adjoin self-serve fails for pre-created computer with hostname > 15 chars with error:get creds: Client not found in Kerberos database articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-6050: How to configure a group for automatic Kerberos Credentials for infinite renewal? articleKB-6044: How to configure users for automatic Kerberos Credentials for infinite renewal even after users have logged out? articleKB-3925: How to add Centrify parameter to a group policy