Applies to: All versions of Centrify DirectControl.
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"
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.
Ticket cache: FILE:/tmp/krb5cc_10063
Default principal: firstname.lastname@example.org
Valid starting Expires Service principal
09/14/10 13:12:13 09/14/10 23:12:13 email@example.com
renew until 09/21/10 13:12:13
-bash-3.00$ kinit smith
Password for firstname.lastname@example.org:
-bash-3.00$ kinit bsmith
kinit(v5): Client not found in Kerberos database while getting initial credentials
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.
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