kinit is an utility that permits to obtain and cache Kerberos ticket-granting tickets.
You can then verify that the Kerberos configuration is good and that the authentication is working.
kinit assumes you want tickets for your own username in your default realm.
kinit
Password for [email protected]:
New ticket is stored in cache file C:\Users\gerard\krb5cc_gerard
A friend David is visiting, and he wants to borrow a window to check his mail. David needs to get tickets for himself in his own realm.
kinit [email protected]
Password for [email protected]:
kinit -V -k -t /path/To/keyTabFile principal
Authenticated to Kerberos v5
/usr/kerberos/bin/kinit
>where kinit
C:\Program Files\Java\jdk1.8.0_05\bin\kinit.exe
Usage:
>kinit -help
Usage: kinit [-A] [-f] [-p] [-c cachename] [[-k [-t keytab_file_name]] [principal] [password]
available options to Kerberos 5 ticket request:
-A do not include addresses
-f forwardable
-p proxiable
-c cache name (i.e., FILE:\d:\myProfiles\mykrb5cache)
-k use keytab
-t keytab file name
principal the principal name (i.e., [email protected] qweadf)
password the principal's Kerberos password
where:
Generally the error “KDC has no support for encryption type” has nothing to do with the encryption type itself but with access to the credentials (ie bad domain controller host, …). It's a very misleading error message.
“Key table entry not found” means that the client presented a service ticket whose contents don't match anything in the server's keytab file.
In this scenario the most likely reason is that: