hi,
problem solved. This was indeed a replay cache file. Using a true
ccache one solved the issue.
Thanks for your assistance.
--
groet,
natxo
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
On Fri, Oct 10, 2014 at 12:28 AM, Tom Yu wrote:
> Natxo Asenjo writes:
>
>> When implementing rsyslog with gssapi
>> (http://www.rsyslog.com/doc/gssapi.html) I came accross the issue
>> that the rsyslog software expects the credentials cache of the host
>> principal in /tmp/krb5cc_0; the centos
On Thu, 2014-10-09 at 23:10 +0200, Natxo Asenjo wrote:
> hi,
>
> When implementing rsyslog with gssapi
> (http://www.rsyslog.com/doc/gssapi.html) I came accross the issue
> that the rsyslog software expects the credentials cache of the host
> principal in /tmp/krb5cc_0; the centos 6.5 hosts joine
Natxo Asenjo writes:
> When implementing rsyslog with gssapi
> (http://www.rsyslog.com/doc/gssapi.html) I came accross the issue
> that the rsyslog software expects the credentials cache of the host
> principal in /tmp/krb5cc_0; the centos 6.5 hosts joined to a freeipa
> kerberos domain save tha
hi,
When implementing rsyslog with gssapi
(http://www.rsyslog.com/doc/gssapi.html) I came accross the issue
that the rsyslog software expects the credentials cache of the host
principal in /tmp/krb5cc_0; the centos 6.5 hosts joined to a freeipa
kerberos domain save that to /var/tmp/host_0 .
I tr
