You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "winkidzz (Jira)" <ji...@apache.org> on 2020/07/15 13:46:00 UTC

[jira] [Created] (KAFKA-10276) Kafka kerberos caching key tabs in default instance not kerberos service name for multi cluster configuration

winkidzz created KAFKA-10276:
--------------------------------

             Summary: Kafka kerberos caching key tabs in default instance not kerberos service name for multi cluster configuration
                 Key: KAFKA-10276
                 URL: https://issues.apache.org/jira/browse/KAFKA-10276
             Project: Kafka
          Issue Type: Bug
          Components: clients
    Affects Versions: 2.4.1, 2.5.0
            Reporter: winkidzz


The spring cloud stream multi binder configuration to connect a service to two different clusters does not work properly. SCST passes the broker configuration to KafkaClient library. Since the key tabs are cached in hash map internally, the kafka client library lookup returns cached key tab and cached service name. The current configuration has different service name that is used to connect to second cluster causing failure.

 

Note: Keytab configuration in the service is same to connect to all the clusters.

 

More information at https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/924



--
This message was sent by Atlassian Jira
(v8.3.4#803005)