Spring Security 6 & JWT Authentication · Aula

Entendendo codificadores de senhas

Examine os diferentes codificadores de senhas disponíveis no Spring Security e sua importância para armazenar senhas com segurança.

Entendendo codificadores de senhas é uma aula grátis de Spring Security 6 & JWT Authentication no CoddyKit. Esta é a aula 2 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 Spring Security 6 & JWT Authentication, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Spring Security 6 & JWT Authentication inclui 4 aulas no total.

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

Why Encode Passwords?

Imagine storing your password in a simple text file. Anyone who gains access to that file can immediately see and use your password.

This is a major security risk! In web applications, we never store user passwords in plain, readable text.

Hashing vs. Encryption

When we talk about securing passwords, we use a technique called hashing, not encryption. What's the difference?

Encryption: Reversible process. You can encrypt data and later decrypt it back to its original form using a key.
Hashing: One-way process. You transform data into a fixed-size string (a hash) that is extremely difficult to reverse. There's no 'decrypting' a hash.

Hashing ensures that even if a database is breached, attackers only get hashes, not actual passwords.

Spring Security's Role

Spring Security provides powerful tools to handle password encoding correctly and securely. It uses a special component called a Password Encoder.

This encoder takes a plain-text password and converts it into a secure hash before storing it. When a user tries to log in, Spring Security encodes their entered password and compares the new hash with the stored hash.

The PasswordEncoder Interface

At the core of Spring Security's password handling is the PasswordEncoder interface. Any class that implements this interface can be used to encode and verify passwords.

It defines two main methods:

encode(CharSequence rawPassword): Creates a hash of the raw password.
matches(CharSequence rawPassword, String encodedPassword): Checks if a raw password matches an encoded password.

Introducing BCryptPasswordEncoder

One of the most widely recommended and secure password encoders in Spring Security is BCryptPasswordEncoder.

Why is BCrypt so good?

Salting: It automatically adds a random 'salt' to each password before hashing, making identical passwords produce different hashes.
Adaptive Hashing: It's designed to be computationally intensive, which slows down brute-force attacks. You can even configure its 'strength'.

Encoding a Password with BCrypt

Let's see BCryptPasswordEncoder in action. We'll create an instance and use its encode() method.

Notice how the output is different each time, even for the same input, thanks to salting!

import org.springframework.security.crypto.bcrypt.BCryptPasswordEncoder;

public class PasswordEncoderDemo {
  public static void main(String[] args) {
    BCryptPasswordEncoder encoder = new BCryptPasswordEncoder();
    String rawPassword = "mysecretpassword";

    String encodedPassword1 = encoder.encode(rawPassword);
    String encodedPassword2 = encoder.encode(rawPassword);

    System.out.println("Encoded 1: " + encodedPassword1);
    System.out.println("Encoded 2: " + encodedPassword2);
  }
}

Verifying a Password with BCrypt

When a user attempts to log in, you don't re-encode their password and compare the strings directly. Instead, you use the matches() method.

This method takes the raw password entered by the user and the stored encoded password, then performs the necessary checks securely.

import org.springframework.security.crypto.bcrypt.BCryptPasswordEncoder;

public class PasswordVerifierDemo {
  public static void main(String[] args) {
    BCryptPasswordEncoder encoder = new BCryptPasswordEncoder();
    String rawPassword = "userpass";
    String storedEncodedPassword = encoder.encode(rawPassword);

    System.out.println("Stored Encoded: " + storedEncodedPassword);

    // Simulate login attempt with correct password
    boolean matchesCorrect = encoder.matches("userpass", storedEncodedPassword);
    System.out.println("Matches 'userpass': " + matchesCorrect);

    // Simulate login attempt with incorrect password
    boolean matchesIncorrect = encoder.matches("wrongpass", storedEncodedPassword);
    System.out.println("Matches 'wrongpass': " + matchesIncorrect);
  }
}

Other Secure Encoders

While BCrypt is very common, Spring Security also supports other strong password hashing algorithms. These include:

Pbkdf2PasswordEncoder: Uses PBKDF2 (Password-Based Key Derivation Function 2).
SCryptPasswordEncoder: Based on scrypt, designed to be resistant to GPU-based attacks.
Argon2PasswordEncoder: Uses Argon2, winner of the Password Hashing Competition.

These all serve the same purpose: securely hashing passwords to prevent easy cracking.

DelegatingPasswordEncoder

Spring Security 5.0 introduced DelegatingPasswordEncoder as the default. This is a very important concept!

It allows you to:

Support multiple encoding formats simultaneously (e.g., if you're migrating from an older algorithm).
Define a default encoder while still being able to verify passwords encoded with other algorithms.

It prefixes the encoded password with an identifier (e.g., {bcrypt}) to indicate which algorithm was used.

Quick Check: Password Security

You've learned about the importance of password encoding. Let's test your understanding!

Recap: Secure Password Storage

In this lesson, we explored the critical role of password encoders in Spring Security:

Passwords must always be hashed, not encrypted, for secure storage.
The PasswordEncoder interface defines how passwords are encoded and verified.
BCryptPasswordEncoder is a strong, recommended encoder that uses salting and adaptive hashing.
DelegatingPasswordEncoder allows for flexible support of multiple hashing algorithms.

Proper password encoding is fundamental to protecting user accounts in any application.

Perguntas Frequentes

A aula “Entendendo codificadores de senhas” é grátis?

Sim — o texto completo de “Entendendo codificadores de senhas” é 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 Spring Security 6 & JWT Authentication, atualize para CoddyKit PRO. O curso de Spring Security 6 & JWT Authentication inclui 4 aulas no total.

O que vou aprender em “Entendendo codificadores de senhas”?

Examine os diferentes codificadores de senhas disponíveis no Spring Security e sua importância para armazenar senhas com segurança. Você pratica Spring Security 6 & JWT Authentication 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 Spring Security 6 & JWT Authentication?

Nenhuma experiência prévia é necessária. Spring Security 6 & JWT Authentication 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 2 de 4.

Quanto tempo leva a aula “Entendendo codificadores de senhas”?

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 Spring Security 6 & JWT Authentication?

Sim. Cada aula de Spring Security 6 & JWT Authentication 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

Implementação personalizada de UserDetailsService
Entendendo codificadores de senhas
Integração do gerenciamento de usuários com banco de dados
Autorização baseada em funções com Granted Authorities

← Voltar para Spring Security 6 & JWT Authentication