On 10/26/2011 01:08 PM, fafaforza wrote:
>     # kprop -r JABBER.DOMAIN.NET -f DUMP.FILE -s /etc/krb5.jabber.keytab
>     -d kerberos-ha.domain.net
>     kprop: Client not found in Kerberos database while getting initial
>     ticket

You didn't mention what version of Kerberos you're using.  If it's MIT
krb5 1.9.x, you can set KRB5_TRACE to a filename and get more
information about what kprop is trying to do.

I would expect the client principal to be
host/[email protected], which you say exists, so I'm
not sure what the issue is.  DNS configuration issues could cause the
second component of that principal to be different, but I'd expect that
to affect kprop attempts for the first realm as well.

________________________________________________
Kerberos mailing list           [email protected]
https://mailman.mit.edu/mailman/listinfo/kerberos

Reply via email to