Why Password encoding with BCrypt in Spring Boot? - Purpose & Use Cases

The Big Idea

What if your users' passwords were stolen in plain text? Learn how BCrypt keeps them safe effortlessly.

The Scenario

Imagine storing user passwords as plain text in your database. When someone logs in, you check their password by comparing the text directly.

It feels simple at first, but what if someone hacks your database? All passwords are exposed instantly.

The Problem

Storing plain passwords is risky and careless. Manually hashing passwords with weak methods is slow and often done incorrectly.

This leads to security holes, making user accounts vulnerable to theft and misuse.

The Solution

BCrypt automatically hashes passwords with a strong, slow algorithm and adds a unique salt each time.

This means even if hackers get your data, they cannot easily reverse the passwords.

Before vs After

✗ Before

String storedPassword = userInput; // plain text storage
if (storedPassword.equals(inputPassword)) { allowAccess(); }

✓ After

String hashed = bCryptPasswordEncoder.encode(inputPassword);
if (bCryptPasswordEncoder.matches(inputPassword, hashed)) { allowAccess(); }

What It Enables

It enables secure password storage that protects users even if your database is compromised.

Real Life Example

When you sign up on a website, your password is never saved as plain text. Instead, BCrypt safely encodes it so only you can access your account.

Key Takeaways

Storing plain passwords is dangerous and easy to exploit.

Manual hashing is error-prone and often weak.

BCrypt provides strong, salted, and slow hashing to protect passwords securely.