[KAFKA-1684] Implement TLS/SSL authentication

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: 0.9.0.0
• Component/s: security
• Assignee: Harsha
• Reporter: Jay Kreps
• Created: 07/Oct/14 23:50
• Updated: 05/Aug/15 14:03
• Resolved: 04/Aug/15 14:27

Description

Add an SSL port to the configuration and advertise this as part of the metadata request.

If the SSL port is configured the socket server will need to add a second Acceptor thread to listen on it. Connections accepted on this port will need to go through the SSL handshake prior to being registered with a Processor for request processing.

SSL requests and responses may need to be wrapped or unwrapped using the SSLEngine that was initialized by the acceptor. This wrapping and unwrapping is very similar to what will need to be done for SASL-based authentication schemes. We should have a uniform interface that covers both of these and we will need to store the instance in the session with the request. The socket server will have to use this object when reading and writing requests. We will need to take care with the FetchRequests as the current FileChannel.transferTo mechanism will be incompatible with wrap/unwrap so we can only use this optimization for unencrypted sockets that don't require userspace translation (wrapping).

Issue Links

• is blocked by: KAFKA-1477 add authentication layer and initial JKS x509 implementation for brokers, producers and consumer for network communication
• is blocked by: KAFKA-1690 Add SSL support to Kafka Broker, Producer and Consumer
• is blocked by: KAFKA-1691 new java consumer needs ssl support as a client
• is blocked by: KAFKA-1928 Move kafka.network over to using the network classes in org.apache.kafka.common.network
• is duplicated by: KAFKA-1690 Add SSL support to Kafka Broker, Producer and Consumer