0Pricing
Spring Security 6 & JWT Authentication · Pelajaran

Memahami Pengode Kata Sandi

Pelajari berbagai pengode kata sandi yang tersedia di Spring Security dan pentingnya bagi penyimpanan kata sandi yang aman.

Memahami Pengode Kata Sandi adalah pelajaran Spring Security 6 & JWT Authentication gratis di CoddyKit. Ini adalah pelajaran 2 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Spring Security 6 & JWT Authentication, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Spring Security 6 & JWT Authentication mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

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.

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Memahami Pengode Kata Sandi” gratis?

Ya — teks lengkap “Memahami Pengode Kata Sandi” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Spring Security 6 & JWT Authentication, upgrade ke CoddyKit PRO. Kursus Spring Security 6 & JWT Authentication mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Memahami Pengode Kata Sandi”?

Pelajari berbagai pengode kata sandi yang tersedia di Spring Security dan pentingnya bagi penyimpanan kata sandi yang aman. Kamu berlatih Spring Security 6 & JWT Authentication dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai Spring Security 6 & JWT Authentication?

Tidak diperlukan pengalaman sebelumnya. Spring Security 6 & JWT Authentication di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 2 dari 4.

Berapa lama pelajaran “Memahami Pengode Kata Sandi” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran Spring Security 6 & JWT Authentication ini?

Ya. Setiap pelajaran Spring Security 6 & JWT Authentication menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

  1. Implementasi UserDetailsService Kustom
  2. Memahami Pengode Kata Sandi
  3. Integrasi Pengelolaan Pengguna Basis Data
  4. Otorisasi Berbasis Peran dengan Granted Authorities
← Kembali ke Spring Security 6 & JWT Authentication