Why Password hashing with bcrypt in FastAPI? - Purpose & Use Cases

The Big Idea

What if your password database got stolen--would your users still be safe?

The Scenario

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

Sounds simple, right? But what if your database is hacked? All passwords are instantly exposed.

The Problem

Storing plain passwords is risky and careless. If a hacker gets access, they steal all user passwords easily.

Also, manually trying to encrypt or protect passwords without a strong method is complicated and often done wrong, leaving security holes.

The Solution

Using bcrypt to hash passwords means you never store the actual password, only a scrambled version that is very hard to reverse.

This keeps user data safe even if the database leaks, because the real passwords cannot be easily found.

Before vs After

✗ Before

stored_password = input_password  # plain text storage
if input_password == stored_password:
    allow_access()

✓ After

hashed = bcrypt.hashpw(input_password.encode(), bcrypt.gensalt())
if bcrypt.checkpw(input_password.encode(), hashed):
    allow_access()

What It Enables

It enables secure user authentication that protects sensitive data from theft and misuse.

Real Life Example

When you sign up on a website, your password is hashed with bcrypt before saving. Even if hackers steal the database, they cannot see your real password.

Key Takeaways

Never store plain text passwords.

Bcrypt hashes passwords securely with salt.

This protects users even if data leaks happen.