has_secure_password in Ruby on Rails - Step-by-Step Execution

Concept Flow - has_secure_password

Model includes has_secure_password

↓

Adds password and password_confirmation virtual attributes

↓

On save: password is hashed with bcrypt

↓

Stores hashed password in password_digest column

↓

Authenticate method checks password against digest

↓

Returns user if password matches, else false

This flow shows how has_secure_password adds password handling to a model, hashes the password, stores it securely, and authenticates users.

Execution Sample

Ruby on Rails

class User < ApplicationRecord
  has_secure_password
end

user = User.new(password: "secret", password_confirmation: "secret")
user.save
user.authenticate("secret")

This code creates a User with a password, saves it securely, and authenticates the password.

Execution Table

Step	Action	Input/Condition	Result	Notes
1	Create User instance	password: 'secret', password_confirmation: 'secret'	User object with virtual password attributes	password_digest is nil initially
2	Call save	password and confirmation match	Password hashed and stored in password_digest	bcrypt hashes password securely
3	Call authenticate('secret')	Password matches digest	Returns User object	Authentication successful
4	Call authenticate('wrong')	Password does not match digest	Returns false	Authentication failed

💡 Authentication returns false when password does not match stored digest

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
user.password	nil	"secret"	nil	nil	nil
user.password_confirmation	nil	"secret"	nil	nil	nil
user.password_digest	nil	nil	"$2a$...hashed..."	"$2a$...hashed..."	"$2a$...hashed..."
authenticate result	n/a	n/a	n/a	User object	false

Key Moments - 3 Insights

Why don't we see the plain password saved in the database?

Because has_secure_password stores only the hashed password in password_digest, not the plain password. See execution_table step 2 where password_digest is set after hashing.

What happens if password and password_confirmation do not match?

The save will fail because has_secure_password validates that password and confirmation match before hashing. This is implied in execution_table step 2 condition.

What does authenticate return if the password is wrong?

It returns false, as shown in execution_table step 4, indicating authentication failure.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of user.password_digest after saving the user?

A A hashed string starting with $2a$

B The plain text password 'secret'

C nil

D The password_confirmation value

💡 Hint

Check execution_table row 2 under Result column

At which step does authenticate return false?

A Step 1

B Step 3

C Step 4

D Step 2

💡 Hint

Look at execution_table rows 3 and 4 for authenticate results

If password_confirmation did not match password, what would happen during save?

A User saves successfully with hashed password

B Save fails due to validation error

C Password_digest is set to nil

D Authenticate returns true anyway

💡 Hint

Refer to key_moments about password confirmation validation

Concept Snapshot

has_secure_password adds password handling to Rails models.
It creates virtual password and confirmation attributes.
On save, it hashes the password with bcrypt into password_digest.
Authenticate checks password against the digest.
Returns user if correct, false if not.
Requires password_digest column in database.

Full Transcript

The has_secure_password method in Rails adds secure password handling to a model. When you add it, the model gets virtual attributes for password and password_confirmation. When you save the model, it hashes the password using bcrypt and stores the hash in the password_digest column. The plain password is never saved. You can then call authenticate with a password string. If it matches the stored hash, authenticate returns the user object. If not, it returns false. This helps keep passwords safe and easy to check. The password and confirmation must match to save successfully.

Practice

1. What does has_secure_password add to a Rails model?

easy

A. Password encryption and authentication methods

B. Automatic email validation

C. Database indexing for passwords

D. User role management

Solution

1. Step 1: Understand the purpose of has_secure_password

   This method adds password encryption and authentication features to a model.

2. Step 2: Identify what it does not add

   It does not handle email validation, indexing, or roles.

3. Final Answer:

   Password encryption and authentication methods -> Option A

4. Quick Check:

   has_secure_password = Password encryption and authentication [OK]

Hint: Remember it handles passwords securely, not emails or roles [OK]

Common Mistakes:

• Thinking it validates emails
• Assuming it manages user roles
• Believing it creates database indexes

2. Which of the following is the correct way to enable has_secure_password in a Rails model?

easy

A. Add secure_password inside the model class

B. Add has_secure_password inside the model class

C. Add password_digest method inside the model

D. Add encrypt_password in the controller

Solution

1. Step 1: Recall the syntax for enabling password security

   The correct syntax is to call has_secure_password inside the model class.

2. Step 2: Eliminate incorrect options

   The other options use wrong method names or wrong places.

3. Final Answer:

   Add has_secure_password inside the model class -> Option B

4. Quick Check:

   Enable with has_secure_password in model = Add has_secure_password inside the model class [OK]

Hint: Use exact method name inside model class [OK]

Common Mistakes:

• Using wrong method names like secure_password
• Trying to add password_digest as a method
• Placing password logic in controller

3. Given this model code:

class User < ApplicationRecord
  has_secure_password
end

And this code:

user = User.new(password: 'secret', password_confirmation: 'secret')
user.save
user.authenticate('secret')

What will user.authenticate('secret') return?

medium

A. nil

B. false

C. The user object

D. An error

Solution

1. Step 1: Understand authenticate behavior

   It returns the user object if the password matches.

2. Step 2: Check password and confirmation match

   Since password and confirmation are both 'secret', save succeeds and authenticate returns user.

3. Final Answer:

   The user object -> Option C

4. Quick Check:

   Correct password authenticates user object [OK]

Hint: authenticate returns user if password matches, else false [OK]

Common Mistakes:

• Expecting authenticate to return true/false only
• Confusing nil and false return values
• Ignoring password confirmation

4. You added has_secure_password to your model but get this error when saving: ActiveModel::MissingAttributeError: can't write unknown attribute `password_digest`. What is the likely cause?

medium

A. You did not validate password presence

B. You did not call has_secure_password in the model

C. You used password instead of password_digest in the form

D. You forgot to add the password_digest column to the database

Solution

1. Step 1: Understand the error meaning

   The error says the model cannot write to password_digest attribute because it does not exist.

2. Step 2: Identify missing database column

   has_secure_password requires a password_digest column in the database table.

3. Final Answer:

   You forgot to add the password_digest column to the database -> Option D

4. Quick Check:

   Missing password_digest column causes this error [OK]

Hint: Add password_digest column to fix this error [OK]

Common Mistakes:

• Thinking it's a missing method call
• Confusing form field names with database columns
• Assuming validation causes this error

5. You want to create a User model with secure passwords and also ensure users can only update their password if they provide the current password correctly. Which approach correctly combines has_secure_password with this logic?

hard

A. Use has_secure_password and add a custom method to verify current password before update

B. Use has_secure_password and override authenticate to check current password

C. Add password_digest column but handle password encryption manually

D. Use has_secure_password and skip password confirmation validation

Solution

1. Step 1: Understand has_secure_password role

   It provides password encryption and authentication but does not enforce current password checks on update.

2. Step 2: Implement custom logic for current password verification

   You must add a method that checks the current password before allowing password update.

3. Step 3: Evaluate options

   Use has_secure_password and add a custom method to verify current password before update correctly combines has_secure_password with custom verification. Use has_secure_password and override authenticate to check current password incorrectly suggests overriding authenticate. Add password_digest column but handle password encryption manually ignores has_secure_password benefits. Use has_secure_password and skip password confirmation validation weakens security.

4. Final Answer:

   Use has_secure_password and add a custom method to verify current password before update -> Option A

5. Quick Check:

   Combine has_secure_password with custom current password check [OK]

Hint: Add custom method to check current password before update [OK]

Common Mistakes:

• Overriding authenticate method incorrectly
• Handling encryption manually instead of using has_secure_password
• Skipping password confirmation validation