Advanced Spring Boot 4: Event-Driven Architecture (Kafka) · 课时

使用 SSL/TLS 加密

使用 SSL/TLS 加密保护 Kafka 客户端与代理之间传输中的数据，增强机密性

使用 SSL/TLS 加密 是 CoddyKit 上的免费 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Why Secure Kafka Communication?

In Lesson 1 of this mini-course, we learned about authenticating Kafka clients with SASL. Now, let's focus on securing the data itself as it travels between your Spring Boot application and Kafka brokers.

Imagine sending sensitive data over an open network. Without encryption, anyone could potentially intercept and read your messages. This is where SSL/TLS comes in.

Introducing SSL/TLS for Data Privacy

SSL/TLS (Secure Sockets Layer/Transport Layer Security) is a cryptographic protocol designed to provide communication security over a computer network. Think of it as a secure tunnel for your data.

Confidentiality: Prevents unauthorized reading of data.
Integrity: Ensures data isn't tampered with during transit.
Authentication: Verifies the identity of the communicating parties (optional but recommended).

Keystores and Truststores

To enable SSL/TLS, Kafka clients and brokers rely on two main types of credential stores:

Keystore: Contains the private key and digital certificates for the entity (client or broker) to identify itself. It's like your digital passport and its secret key.
Truststore: Contains certificates of trusted Certificate Authorities (CAs) or directly trusted public keys. This allows an entity to verify the identity of another party. It's like a list of authorized passport offices you trust.

Understanding Digital Certificates

A digital certificate is an electronic document used to prove ownership of a public key. It's issued by a Certificate Authority (CA) or can be self-signed for development purposes.

For secure Kafka communication, both your client (Spring Boot app) and the Kafka broker will need certificates. When a client connects, the broker presents its certificate, and the client verifies it using its truststore.

Kafka Broker SSL/TLS Configuration (Overview)

While our focus is Spring Boot, it's important to know that Kafka brokers must also be configured for SSL/TLS. They need their own keystore and truststore, and a specific secure listener port (e.g., 9093).

When your Spring Boot application connects, it will use this secure port and exchange certificates to establish an encrypted connection. This setup is typically done by a Kafka administrator.

Spring Boot Producer SSL Setup

To configure your Spring Boot Kafka producer for SSL/TLS, you'll add properties to your application.properties or application.yml file. These tell Spring Kafka where to find the necessary certificates.

Here are the key properties:

spring.kafka.producer.bootstrap-servers=localhost:9093
spring.kafka.properties.security.protocol=SSL
spring.kafka.properties.ssl.truststore.location=file:/path/to/client.truststore.jks
spring.kafka.properties.ssl.truststore.password=your-truststore-password
# Optional: for mutual TLS (client authentication)
spring.kafka.properties.ssl.keystore.location=file:/path/to/client.keystore.jks
spring.kafka.properties.ssl.keystore.password=your-keystore-password
spring.kafka.properties.ssl.key.password=your-key-password

Spring Boot Consumer SSL Setup

Similarly, your Spring Boot Kafka consumer needs the same SSL/TLS configuration to connect securely. The properties are largely identical, ensuring both sides of your application can speak securely to the Kafka broker.

Remember to point to the correct keystore and truststore files for your consumer.

spring.kafka.consumer.bootstrap-servers=localhost:9093
spring.kafka.properties.security.protocol=SSL
spring.kafka.properties.ssl.truststore.location=file:/path/to/client.truststore.jks
spring.kafka.properties.ssl.truststore.password=your-truststore-password
# Optional: for mutual TLS (client authentication)
spring.kafka.properties.ssl.keystore.location=file:/path/to/client.keystore.jks
spring.kafka.properties.ssl.keystore.password=your-keystore-password
spring.kafka.properties.ssl.key.password=your-key-password

spring.kafka.consumer.group-id=my-secure-group
spring.kafka.consumer.auto-offset-reset=earliest

Example: Secure Producer Application

Here's a basic Spring Boot application that, when combined with the SSL properties from the previous scene, will attempt to connect to Kafka using SSL/TLS. The security is handled by the configuration, not explicit code changes.

package com.coddykit;

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.context.annotation.Bean;
import org.springframework.kafka.core.KafkaTemplate;
import org.springframework.kafka.core.ProducerFactory;
import org.springframework.kafka.core.DefaultKafkaProducerFactory;
import java.util.HashMap;
import java.util.Map;
import org.apache.kafka.clients.producer.ProducerConfig;
import org.apache.kafka.common.serialization.StringSerializer;

@SpringBootApplication
public class SecureProducerApp {

    public static void main(String[] args) {
        SpringApplication.run(SecureProducerApp.class, args);
        System.out.println("Secure Producer App started.\nCheck application.properties for SSL config!");
    }

    // Spring Boot auto-configures this, but explicit definition helps understanding.
    @Bean
    public ProducerFactory<String, String> producerFactory() {
        Map<String, Object> configProps = new HashMap<>();
        configProps.put(ProducerConfig.BOOTSTRAP_SERVERS_CONFIG, "localhost:9093");
        configProps.put(ProducerConfig.KEY_SERIALIZER_CLASS_CONFIG, StringSerializer.class);
        configProps.put(ProducerConfig.VALUE_SERIALIZER_CLASS_CONFIG, StringSerializer.class);
        // SSL properties are loaded automatically from application.properties
        return new DefaultKafkaProducerFactory<>(configProps);
    }

    @Bean
    public KafkaTemplate<String, String> kafkaTemplate() {
        return new KafkaTemplate<>(producerFactory());
    }
}

Example: Secure Consumer Application

Similarly, a consumer application uses the same configuration properties to establish a secure connection. The @KafkaListener annotation will then automatically pick up messages from the secure topic.

package com.coddykit;

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.kafka.annotation.KafkaListener;
import org.springframework.stereotype.Component;

@SpringBootApplication
public class SecureConsumerApp {

    public static void main(String[] args) {
        SpringApplication.run(SecureConsumerApp.class, args);
        System.out.println("Secure Consumer App started.\nCheck application.properties for SSL config!");
    }

    @Component
    public static class MyKafkaListener {
        @KafkaListener(topics = "secure-topic", groupId = "my-secure-group")
        public void listen(String message) {
            System.out.println("Received secure message: " + message);
        }
    }
}

Common SSL/TLS Issues

Configuring SSL/TLS can be tricky. Here are common issues to watch for:

Incorrect Paths: Truststore/Keystore file paths must be correct and accessible.
Wrong Passwords: Passwords for keystores, truststores, or private keys must match exactly.
Untrusted Certificates: The client's truststore must contain the CA certificate that signed the broker's certificate (or the broker's self-signed cert).
Protocol Mismatch: Ensure security.protocol is set to SSL and the Kafka broker is listening on an SSL port.

Quick Check: SSL Properties

Which of the following properties are essential for a Spring Boot Kafka client to establish a secure SSL/TLS connection with a Kafka broker, assuming mutual TLS (client authentication) is enabled on the broker?

Recap & Next Steps

Great job! You've learned how to secure data in transit for your Spring Boot Kafka applications using SSL/TLS.

We covered the importance of SSL/TLS for confidentiality and integrity.
Understood the roles of Keystores and Truststores.
Explored the key application.properties for configuring both secure producers and consumers.
Reviewed common pitfalls when setting up SSL/TLS.

By combining what you've learned about SASL authentication and SSL/TLS encryption, you can build robust and secure Kafka-based microservices.

常见问题解答

「使用 SSL/TLS 加密」课时是免费的吗？

是的 — 「使用 SSL/TLS 加密」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课程的其余内容，请升级到 CoddyKit PRO。 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课程共包含 4 节课。

「使用 SSL/TLS 加密」这节课中我会学到什么？

使用 SSL/TLS 加密保护 Kafka 客户端与代理之间传输中的数据，增强机密性你通过在浏览器中直接运行的动手代码来练习 Advanced Spring Boot 4: Event-Driven Architecture (Kafka)，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 4 节。

「使用 SSL/TLS 加密」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课中编写并运行代码吗？

能。每节 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Advanced Spring Boot 4: Event-Driven Architecture (Kafka)