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

Szyfrowanie za pomocą SSL/TLS

Zabezpiecz dane przesyłane między klientami a brokerami Kafka za pomocą szyfrowania SSL/TLS, zwiększając ich poufność.

Szyfrowanie za pomocą SSL/TLS to bezpłatna lekcja Advanced Spring Boot 4: Event-Driven Architecture (Kafka) na CoddyKit. To lekcja 3 z 4. Możesz przeczytać całą lekcję poniżej za darmo — a potem ćwiczyć ją interaktywnie w przeglądarce z wbudowanym edytorem kodu i tutorem AI dostępnym 24/7. To część ścieżki edukacyjnej Advanced Spring Boot 4: Event-Driven Architecture (Kafka), a Twój postęp synchronizuje się między webem a aplikacją CoddyKit. Kurs Advanced Spring Boot 4: Event-Driven Architecture (Kafka) zawiera 4 lekcji w sumie.

Części tej lekcji nie zostały jeszcze przetłumaczone i są wyświetlane po angielsku.

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.

Często zadawane pytania

Czy lekcja „Szyfrowanie za pomocą SSL/TLS” jest bezpłatna?

Tak — pełny tekst „Szyfrowanie za pomocą SSL/TLS” jest dostępny za darmo tutaj w sieci. Aby ćwiczyć ją interaktywnie (wbudowany edytor kodu i tutor AI dostępny 24/7) i odblokować resztę kursu Advanced Spring Boot 4: Event-Driven Architecture (Kafka), przejdź na CoddyKit PRO. Kurs Advanced Spring Boot 4: Event-Driven Architecture (Kafka) zawiera 4 lekcji w sumie.

Co nauczysz się w „Szyfrowanie za pomocą SSL/TLS”?

Zabezpiecz dane przesyłane między klientami a brokerami Kafka za pomocą szyfrowania SSL/TLS, zwiększając ich poufność. Ćwiczysz Advanced Spring Boot 4: Event-Driven Architecture (Kafka) z praktycznym kodem, który uruchamiasz bezpośrednio w przeglądarce, a tutor AI dostępny 24/7 odpowiada na Twoje pytania podczas pracy nad lekcją.

Czy potrzebuję doświadczenia, aby zacząć Advanced Spring Boot 4: Event-Driven Architecture (Kafka)?

Nie wymagamy żadnego doświadczenia. Advanced Spring Boot 4: Event-Driven Architecture (Kafka) w CoddyKit jest strukturyzowany dla początkujących i zaawansowanych użytkowników, więc możesz zacząć tutaj lub od początku i uczyć się w swoim tempie. To lekcja 3 z 4.

Ile czasu zajmuje lekcja „Szyfrowanie za pomocą SSL/TLS”?

Większość lekcji CoddyKit trwa około 5–10 minut. Każda lekcja to mały, interaktywny krok, dzięki czemu robisz systematyczne postępy i zawsze wracasz dokładnie do tego samego miejsca — na webie i w aplikacji.

Czy mogę pisać i uruchamiać kod w tej lekcji Advanced Spring Boot 4: Event-Driven Architecture (Kafka)?

Tak. Każda lekcja Advanced Spring Boot 4: Event-Driven Architecture (Kafka) zawiera wbudowany edytor kodu, więc piszesz i uruchamiasz prawdziwy kod bezpośrednio w przeglądarce i od razu otrzymujesz sprzężenie zwrotne od AI — bez konfiguracji na komputerze.

Wszystkie lekcje w tym kursie

Uwierzytelnianie za pomocą SASL
Autoryzacja za pomocą ACL
Szyfrowanie za pomocą SSL/TLS
Audytowanie i zabezpieczanie dostępu do Schema Registry

← Powrót do Advanced Spring Boot 4: Event-Driven Architecture (Kafka)