Thanks for all the suggestions.
I got rid of the "-S kafka/host" part, which also removed the credential
not found error. But I still cannot connect to the KafkaServer using the
VM. Maybe someone of you knows if the following log relates to a finally
successful authorization, or if there is still s
Ah I still had a bug, not pointing to the correct keytab_file. Also
discussed here https://github.com/edenhill/librdkafka/issues/1630 and here
https://github.com/cyrusimap/cyrus-sasl/issues/501
It now hangs at an GSSAPI step 1.
```
Using python-kafka: ('0.11.0', 720896) and librdkafka
('0.11.1-10
I'm a newbie and had a similar issue, in order to find out the right
principal for a service, I executed Wireshark on client or server node in a
test env... Wireshark kerberos dissector works quite well and tuo can see
details of requests, principals too. Perhaps this ke obvious but.. Not for
me :-
My best guess is that there is a disagreement between the server
principal name passed to kinit -S ("kafka/host") and the server
principal name chosen by SASL GSSAPI. At least, that's the most obvious
way I can find to get a "Matching credential not found" error message
from MIT krb5's GSSAPI libr
>I have a hard time troubleshooting an error. I posted the issue
>already here (https://github.com/edenhill/librdkafka/issues/1630) and
>here (https://github.com/cyrusimap/cyrus-sasl/issues/501), but to no
>avail.
It might be helpful to describe what the underlying Kerberos implementation
is on th
Hi,
I have a hard time troubleshooting an error. I posted the issue
already here (https://github.com/edenhill/librdkafka/issues/1630) and
here (https://github.com/cyrusimap/cyrus-sasl/issues/501), but to no
avail.
In short:
I try to access a KafkaServer which uses Kerberos for authentication.
