0Pricing
Advanced Spring Boot 4: Event-Driven Architecture (Kafka) · Aula

Autenticação com SASL

Configure clientes Kafka do Spring Boot para autenticação com os intermediários Kafka usando SASL (Camada simples de autenticação e segurança).

Autenticação com SASL é uma aula grátis de Advanced Spring Boot 4: Event-Driven Architecture (Kafka) no CoddyKit. Esta é a aula 1 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Advanced Spring Boot 4: Event-Driven Architecture (Kafka), e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Advanced Spring Boot 4: Event-Driven Architecture (Kafka) inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

What is SASL?

Welcome to securing your Kafka applications! Today, we'll dive into SASL, which stands for Simple Authentication and Security Layer.

SASL is a framework for authentication and data security in network protocols. For Kafka, it's how your clients (like Spring Boot apps) prove their identity to the Kafka brokers.

Why Authenticate with Kafka?

Imagine a bank: you wouldn't want just anyone accessing your accounts. Similarly, in an event-driven system, you need to control who can send or receive messages from your Kafka topics.

  • Prevent Unauthorized Access: Ensure only trusted applications can interact with your Kafka cluster.
  • Data Integrity: Protect your data streams from malicious or accidental interference.
  • Compliance: Meet security requirements for sensitive data processing.

SASL Mechanisms for Kafka

SASL itself is a framework, and it uses specific 'mechanisms' to perform authentication. Common ones for Kafka include:

  • PLAIN: Sends username/password in plaintext (but often over SSL for encryption). Simple, but less secure.
  • SCRAM: (Salted Challenge Response Authentication Mechanism) A more robust, challenge-response mechanism that doesn't send the password directly. Examples: SCRAM-SHA-256, SCRAM-SHA-512.
  • GSSAPI (Kerberos): Enterprise-grade authentication, often used in large corporate environments.

Broker-Side Setup (Conceptual)

Before clients can authenticate, your Kafka brokers must be configured to accept SASL connections. This usually involves:

  • Enabling a SASL listener in server.properties.
  • Configuring a JAAS (Java Authentication and Authorization Service) file for the broker.
  • Defining valid users and their credentials.

While we won't configure the broker here, it's crucial to remember both sides need setup!

Spring Boot Client Properties

For your Spring Boot Kafka client, you'll add security properties to your application.properties or application.yml file. These tell your application how to connect securely.

The main properties are spring.kafka.properties.security.protocol and spring.kafka.properties.sasl.mechanism.

Using SASL_PLAINTEXT

SASL_PLAINTEXT is one of the simplest ways to enable SASL. It sends credentials directly. Often used with SSL (SASL_SSL) to encrypt the connection, making the plaintext credentials secure in transit.

It's good for quick setups or testing, but for production, consider more robust mechanisms like SCRAM.

Here's how you'd configure it in your application.properties:

spring.kafka.producer.properties.sasl.mechanism=PLAIN
spring.kafka.producer.properties.security.protocol=SASL_PLAINTEXT
spring.kafka.producer.properties.sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required username="user" password="password";

SASL_PLAINTEXT Producer Example

This Spring Boot producer sends a simple message using SASL_PLAINTEXT. Remember, the JAAS config would be in application.properties, not directly in code.

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.kafka.core.KafkaTemplate;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.CommandLineRunner;

@SpringBootApplication
public class SaslProducerApplication implements CommandLineRunner {

    @Autowired
    private KafkaTemplate<String, String> kafkaTemplate;

    public static void main(String[] args) {
        SpringApplication.run(SaslProducerApplication.class, args);
    }

    @Override
    public void run(String... args) throws Exception {
        System.out.println("Sending message...");
        kafkaTemplate.send("my-sasl-topic", "Hello from SASL!");
        System.out.println("Message sent with SASL_PLAINTEXT.");
    }
}

Combining SASL with SSL

For production environments, you almost always want to combine SASL authentication with SSL/TLS encryption. This is known as SASL_SSL.

  • Authentication (SASL): Verifies the identity of the client.
  • Encryption (SSL/TLS): Encrypts all data transmitted between the client and the broker, protecting it from eavesdropping.

This provides both identity verification and secure communication, a strong combination for robust security.

Configuring SASL_SSL

When using SASL_SSL, you'll need to specify SSL properties in addition to SASL ones. This includes details about your truststore (to trust the broker's certificate) and potentially a keystore (if the client also needs to authenticate itself with a certificate).

Example application.properties for SASL_SSL (with PLAIN mechanism):

spring.kafka.consumer.properties.security.protocol=SASL_SSL
spring.kafka.consumer.properties.sasl.mechanism=PLAIN
spring.kafka.consumer.properties.sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required username="user" password="password";
spring.kafka.consumer.properties.ssl.truststore.location=file:/path/to/client.truststore.jks
spring.kafka.consumer.properties.ssl.truststore.password=truststore_password

Quick Check

Which of the following is generally considered the most secure SASL mechanism for production environments, especially when combined with SSL?

Recap & Next Steps

Great job! In this lesson, you learned about:

  • What SASL is and why it's vital for Kafka security.
  • Different SASL mechanisms like PLAIN and SCRAM.
  • How to configure Spring Boot Kafka clients for SASL_PLAINTEXT and SASL_SSL.

Remember, securing your Kafka applications is a multi-layered approach. Next, we'll explore how to enforce Authorization with ACLs to control what authenticated users can actually do!

Perguntas Frequentes

A aula “Autenticação com SASL” é grátis?

Sim — o texto completo de “Autenticação com SASL” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Advanced Spring Boot 4: Event-Driven Architecture (Kafka), atualize para CoddyKit PRO. O curso de Advanced Spring Boot 4: Event-Driven Architecture (Kafka) inclui 4 aulas no total.

O que vou aprender em “Autenticação com SASL”?

Configure clientes Kafka do Spring Boot para autenticação com os intermediários Kafka usando SASL (Camada simples de autenticação e segurança). Você pratica Advanced Spring Boot 4: Event-Driven Architecture (Kafka) com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar Advanced Spring Boot 4: Event-Driven Architecture (Kafka)?

Nenhuma experiência prévia é necessária. Advanced Spring Boot 4: Event-Driven Architecture (Kafka) no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 1 de 4.

Quanto tempo leva a aula “Autenticação com SASL”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de Advanced Spring Boot 4: Event-Driven Architecture (Kafka)?

Sim. Cada aula de Advanced Spring Boot 4: Event-Driven Architecture (Kafka) inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

  1. Autenticação com SASL
  2. Autorização com ACLs
  3. Criptografia com SSL/TLS
  4. Auditando e protegendo o acesso ao Schema Registry
← Voltar para Advanced Spring Boot 4: Event-Driven Architecture (Kafka)