Important Warning

Update July 2016: This Tech Preview documentation from March 2016 is outdated and deprecated. Please use the latest Confluent Platform documentation instead.

Adding Security to a Running ClusterΒΆ

You can secure a running cluster via one or more of the supported protocols discussed previously. This is done in phases:

  1. Incrementally bounce the cluster nodes to open additional secured port(s).
  2. Restart clients using the secured rather than PLAINTEXT port (assuming you are securing the client-broker connection).
  3. Incrementally bounce the cluster again to enable broker-to-broker security (if this is required)
  4. A final incremental bounce to close the PLAINTEXT port.

The specific steps for configuring security protocols are described in the respective sections for SSL and SASL. Follow these steps to enable security for your desired protocol(s).

The security implementation lets you configure different protocols for both broker-client and broker-broker communication. These must be enabled in separate bounces. A PLAINTEXT port must be left open throughout so brokers and/or clients can continue to communicate.

When performing an incremental bounce stop the brokers cleanly via a SIGTERM. It’s also good practice to wait for restarted replicas to return to the ISR list before moving onto the next node.

As an example, say we wish to encrypt both broker-client and broker-broker communication with SSL. In the first incremental bounce, a SSL port is opened on each node:


We then restart the clients, changing their config to point at the newly opened, secured port:


In the second incremental server bounce we instruct Kafka to use SSL as the broker-broker protocol (which will use the same SSL port):


In the final bounce we secure the cluster by closing the PLAINTEXT port:


Alternatively we might choose to open multiple ports so that different protocols can be used for broker-broker and broker-client communication. Say we wished to use SSL encryption throughout (i.e. for broker-broker and broker-client communication) but we’d like to add SASL authentication to the broker-client connection also. We would achieve this by opening two additional ports during the first bounce:


Again we would then restart the clients, changing their config to point at the newly opened, SASL & SSL secured port:


The second server bounce would switch the cluster to use encrypted broker-broker communication via the SSL port we previously opened on port 9092:


The final bounce secures the cluster by closing the PLAINTEXT port.


ZooKeeper can be secured independently of the Kafka cluster. The steps for doing this are covered in the ZooKeeper section.