You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Sriharsha Chintalapani (JIRA)" <ji...@apache.org> on 2018/06/28 17:06:00 UTC

[jira] [Resolved] (KAFKA-7116) Provide separate SSL configs for Kafka Broker replication

     [ https://issues.apache.org/jira/browse/KAFKA-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sriharsha Chintalapani resolved KAFKA-7116.
-------------------------------------------
    Resolution: Implemented

Thanks [~ijuma]

> Provide separate SSL configs for Kafka Broker replication
> ---------------------------------------------------------
>
>                 Key: KAFKA-7116
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7116
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Sriharsha Chintalapani
>            Assignee: GEORGE LI
>            Priority: Major
>
> Currently, we are using one set of SSL configs in server.properties for the broker to accept the connections and replication to use as client side as well. For the most part, we can use the server configs for the replication client as well but there are cases where we need separation. 
> Example Inter-broker connections would like to have SSL authentication but want to disable encryption for replication. This is not possible right now due to same config name "cipher_suites" being used for both server and client.  
> Since this Jira introduces new configs we will add a KIP.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)