Password encoding with BCrypt in Spring Boot - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is BCrypt in the context of password encoding?

BCrypt is a password hashing function designed to securely encode passwords by adding a salt and using multiple rounds of hashing to protect against brute-force attacks.

beginner

How do you create a BCrypt password encoder in Spring Boot?

You create a BCrypt password encoder by defining a bean like this:

@Bean
public PasswordEncoder passwordEncoder() {
    return new BCryptPasswordEncoder();
}

intermediate

Why is it important to use a salt in password encoding?

A salt adds random data to the password before hashing, making each hash unique even if two users have the same password. This prevents attackers from using precomputed tables to crack passwords.

beginner

How do you verify a raw password against a BCrypt encoded password in Spring Boot?

Use the matches method of PasswordEncoder:

passwordEncoder.matches(rawPassword, encodedPassword)

It returns true if the raw password matches the encoded one.

intermediate

What is the default strength (log rounds) of BCryptPasswordEncoder in Spring Boot?

The default strength is 10, which means 2^10 (1024) rounds of hashing are applied to make password encoding slower and more secure.

What does BCrypt add to passwords before hashing to improve security?

A A timestamp

B A fixed prefix

C A random salt

D A user ID

BCrypt adds a random salt to each password before hashing to ensure uniqueness and prevent rainbow table attacks.

Which Spring Boot class is commonly used for BCrypt password encoding?

A PasswordEncoderFactory

B PasswordHasher

C HashingService

D BCryptPasswordEncoder

BCryptPasswordEncoder is the standard Spring Boot class for encoding passwords with BCrypt.

How do you check if a raw password matches an encoded BCrypt password in Spring Boot?

A passwordEncoder.matches(raw, encoded)

B passwordEncoder.encode(raw) == encoded

C passwordEncoder.verify(raw, encoded)

D passwordEncoder.check(raw, encoded)

The matches method compares a raw password with an encoded one and returns true if they match.

What is the effect of increasing the strength parameter in BCryptPasswordEncoder?

A It changes the hash algorithm to SHA-256

B It increases the number of hashing rounds, making encoding slower and more secure

C It disables salting

D It decreases the password length

Increasing strength increases the number of hashing rounds, which slows down encoding but improves security.

Why should you never store raw passwords in your database?

A Because raw passwords can be stolen and used directly by attackers

B Because raw passwords take more space

C Because raw passwords are hard to read

D Because raw passwords are encrypted automatically

Storing raw passwords is dangerous because if the database is compromised, attackers get direct access to user passwords.

Explain how BCrypt protects passwords and why it is preferred over simple hashing.

Think about how adding randomness and time cost helps security.

Describe how to implement password encoding and verification using BCrypt in a Spring Boot application.

Focus on the key methods and bean setup.

Practice

1. What is the main purpose of using BCryptPasswordEncoder in Spring Boot?

easy

A. To validate email addresses

B. To decode passwords back to plain text

C. To generate random passwords for users

D. To securely encode passwords before storing them

Solution

1. Step 1: Understand BCryptPasswordEncoder role

   BCryptPasswordEncoder is used to convert plain passwords into a secure encoded form.

2. Step 2: Identify correct purpose

   It does not decode or generate passwords, only encodes them securely.

3. Final Answer:

   To securely encode passwords before storing them -> Option D

4. Quick Check:

   Password encoding = Secure storage [OK]

Hint: BCrypt encodes, never decodes passwords [OK]

Common Mistakes:

• Thinking BCrypt can decode passwords
• Confusing encoding with password generation
• Using it for unrelated tasks like email validation

2. Which of the following is the correct way to create a BCryptPasswordEncoder instance in Spring Boot?

easy

A. BCryptPasswordEncoder encoder = BCryptPasswordEncoder();

B. BCryptPasswordEncoder encoder = new BCryptPasswordEncoder();

C. BCryptPasswordEncoder encoder = new BCryptPasswordEncoder.encode();

D. BCryptPasswordEncoder encoder = encode(new BCryptPasswordEncoder());

Solution

1. Step 1: Recall Java object creation syntax

   In Java, to create an object, use the new keyword followed by the constructor.

2. Step 2: Match correct syntax

   BCryptPasswordEncoder encoder = new BCryptPasswordEncoder(); correctly uses new BCryptPasswordEncoder(); to create an instance.

3. Final Answer:

   BCryptPasswordEncoder encoder = new BCryptPasswordEncoder(); -> Option B

4. Quick Check:

   Object creation = new + constructor [OK]

Hint: Use 'new' keyword to create objects in Java [OK]

Common Mistakes:

• Omitting 'new' keyword when creating objects
• Calling methods instead of constructors
• Incorrect method chaining in object creation

3. Given the following code snippet, what will be the output of matches method?

BCryptPasswordEncoder encoder = new BCryptPasswordEncoder();
String rawPassword = "mypassword";
String encodedPassword = encoder.encode(rawPassword);
boolean result = encoder.matches("mypassword", encodedPassword);
System.out.println(result);

medium

A. true

B. false

C. Compilation error

D. Runtime exception

Solution

1. Step 1: Understand encode and matches methods

   The encode method creates a hashed password. The matches method checks if the raw password matches the encoded hash.

2. Step 2: Analyze the code flow

   The raw password "mypassword" is encoded, then matches compares the same raw password with the encoded one, so it returns true.

3. Final Answer:

   true -> Option A

4. Quick Check:

   matches(raw, encoded) = true if same password [OK]

Hint: matches() returns true if raw matches encoded password [OK]

Common Mistakes:

• Assuming encode returns plain text
• Thinking matches compares encoded strings directly
• Expecting false because encoded password looks different

4. Identify the error in the following Spring Boot code snippet for password encoding:

BCryptPasswordEncoder encoder;
String encoded = encoder.encode("secret");

medium

A. String type cannot hold encoded password

B. encode method does not exist in BCryptPasswordEncoder

C. encoder is not initialized before use

D. Missing import statement for BCryptPasswordEncoder

Solution

1. Step 1: Check variable initialization

   The variable encoder is declared but not assigned an instance before calling encode.

2. Step 2: Understand consequences

   Using an uninitialized object causes a NullPointerException at runtime.

3. Final Answer:

   encoder is not initialized before use -> Option C

4. Quick Check:

   Uninitialized objects cause runtime errors [OK]

Hint: Always initialize objects before calling methods [OK]

Common Mistakes:

• Forgetting to create new instance with 'new'
• Assuming declaration equals initialization
• Ignoring runtime NullPointerException

5. You want to store user passwords securely in your Spring Boot application. Which approach correctly uses BCryptPasswordEncoder to encode and verify passwords during login?

hard

A. Encode password on registration, store encoded; on login, use matches(rawPassword, storedEncodedPassword)

B. Store plain password; on login, encode input and compare with stored plain password

C. Encode password on registration, store encoded; on login, encode input and compare encoded strings directly

D. Encode password on registration, store encoded; on login, decode stored password and compare with input

Solution

1. Step 1: Understand secure password storage

   Passwords must be encoded before storing; plain text storage is insecure.

2. Step 2: Verify password correctly on login

   Use matches(rawPassword, storedEncodedPassword) to check if input matches stored hash without decoding.

3. Final Answer:

   Encode password on registration, store encoded; on login, use matches(rawPassword, storedEncodedPassword) -> Option A

4. Quick Check:

   Use matches() to verify passwords securely [OK]

Hint: Use matches() to check raw vs encoded passwords [OK]

Common Mistakes:

• Comparing encoded strings directly (they differ each time)
• Storing plain text passwords
• Trying to decode encoded passwords (not possible)