فهم مشفّرات كلمات المرور

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.

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 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.

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.

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'.

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!

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.

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.

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.

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

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.