Session-based authentication in Ruby on Rails - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is session-based authentication in Rails?

It is a way to keep a user logged in by storing their user ID in a session cookie on the browser. The server checks this session to know who the user is on each request.

beginner

How does Rails store session data by default?

Rails stores session data in a cookie on the user's browser, which is encrypted and signed to keep it secure.

beginner

What is the role of the 'session' hash in Rails controllers?

The 'session' hash lets you save and access data that persists between requests, like the current user's ID for authentication.

beginner

Why is it important to clear the session on logout?

Clearing the session removes the user's ID and other data, preventing unauthorized access if someone else uses the same browser.

intermediate

What is a common security risk with session-based authentication and how can Rails help prevent it?

Session hijacking is a risk where someone steals the session cookie. Rails helps prevent this by encrypting and signing cookies and using secure and HttpOnly flags.

In Rails, where is the session data usually stored by default?

A In an encrypted cookie on the user's browser

B In the database

C In a server-side file

D In localStorage

By default, Rails stores session data in an encrypted and signed cookie on the user's browser.

What does the 'session[:user_id]' typically store in a Rails app using session-based authentication?

A The current user's ID

B The user's password

C The user's email

D The session expiration time

The session[:user_id] stores the ID of the logged-in user to identify them on future requests.

What should happen to the session when a user logs out in a Rails app?

A Nothing, the session stays the same

B The session should be cleared or reset

C The session should be sent to the database

D The session should be saved permanently

Clearing the session on logout removes user data and prevents unauthorized access.

Which Rails method is commonly used to clear the session?

A destroy_session

B clear_session

C remove_session

D reset_session

The reset_session method clears all session data safely.

Why does Rails encrypt and sign session cookies?

A To speed up the website

B To make cookies larger

C To prevent tampering and protect user data

D To allow cookies to be shared across domains

Encryption and signing keep session cookies secure from tampering and spying.

Explain how session-based authentication works in a Rails application.

Think about what happens when a user logs in and how Rails remembers them.

Describe the security measures Rails uses to protect session data.

Consider how Rails keeps session cookies safe from theft or tampering.

Practice

1. What does session[:user_id] typically store in a Rails application using session-based authentication?

easy

A. The user's password

B. The user's email address

C. The ID of the currently logged-in user

D. The entire user object

Solution

1. Step 1: Understand session usage in Rails

   Rails uses the session hash to store small pieces of data between requests, commonly the user ID for authentication.

2. Step 2: Identify what session[:user_id] holds

   This key stores the unique identifier of the logged-in user to recognize them on subsequent requests.

3. Final Answer:

   The ID of the currently logged-in user -> Option C

4. Quick Check:

   session[:user_id] = user ID [OK]

Hint: Remember session stores user ID, not full user data [OK]

Common Mistakes:

• Thinking session stores full user object
• Confusing user ID with password or email
• Assuming session is client-side storage

2. Which of the following is the correct way to log out a user by clearing the session in a Rails controller?

easy

A. session.clear

B. All of the above

C. session[:user_id] = nil

D. session.delete(:user_id)

Solution

1. Step 1: Review methods to clear session data

   In Rails, you can remove session data by clearing all keys, deleting a specific key, or setting a key to nil.

2. Step 2: Confirm all options effectively log out user

   All three methods remove the user ID from session, effectively logging out the user.

3. Final Answer:

   All of the above -> Option B

4. Quick Check:

   Any method removing user_id logs out user [OK]

Hint: Any method removing session[:user_id] logs out user [OK]

Common Mistakes:

• Only using session[:user_id] = nil and ignoring others
• Trying to clear session without removing user_id
• Confusing session.clear with resetting entire app

3. Given this Rails controller code snippet:

def create
  user = User.find_by(email: params[:email])
  if user&.authenticate(params[:password])
    session[:user_id] = user.id
    redirect_to dashboard_path
  else
    render :new
  end
end

What happens when the user enters correct email and password?

medium

A. User ID is saved in session and redirected to dashboard

B. User is redirected to login page again

C. Session is cleared and user stays on login page

D. An error is raised because session[:user_id] is not set

Solution

1. Step 1: Analyze authentication condition

   The code checks if a user with the given email exists and if the password matches using authenticate.

2. Step 2: Understand session assignment and redirect

   If authentication passes, it stores the user's ID in session and redirects to the dashboard.

3. Final Answer:

   User ID is saved in session and redirected to dashboard -> Option A

4. Quick Check:

   Correct login sets session[:user_id] and redirects [OK]

Hint: Correct login sets session[:user_id] and redirects [OK]

Common Mistakes:

• Assuming user stays on login page after success
• Thinking session[:user_id] is not set on success
• Confusing render with redirect behavior

4. Identify the error in this logout action:

def logout
  session[:user] = nil
  redirect_to root_path
end

medium

A. No error, this code works fine

B. redirect_to should be redirect_back

C. session[:user] = nil does not clear session

D. Session key should be :user_id, not :user

Solution

1. Step 1: Check session key used for authentication

   Rails session-based authentication typically uses session[:user_id] to track logged-in user.

2. Step 2: Identify mismatch in session key

   The code sets session[:user] to nil, which does not clear the actual user ID stored in session[:user_id].

3. Final Answer:

   Session key should be :user_id, not :user -> Option D

4. Quick Check:

   Correct session key is :user_id [OK]

Hint: Use session[:user_id] to clear login, not session[:user] [OK]

Common Mistakes:

• Using wrong session key name
• Assuming setting any session key to nil logs out user
• Confusing redirect_to with redirect_back

5. You want to restrict access to a controller action so only logged-in users can see it. Which code snippet correctly checks session-based authentication before allowing access?

hard

A. before_action :require_login

def require_login
redirect_to login_path unless session[:user_id]
end

B. before_action :require_login

def require_login
redirect_to login_path if session[:user_id]
end

C. before_action :require_login

def require_login
redirect_to root_path unless session[:user_id]
end

D. before_action :require_login

def require_login
redirect_to login_path unless session[:user]
end

Solution

1. Step 1: Understand access control with before_action

   Use a method to check if session[:user_id] exists before allowing access.

2. Step 2: Identify correct redirect condition

   If session[:user_id] is missing, redirect to login page to block access.

3. Final Answer:

   Redirect to login unless session[:user_id] exists -> Option A

4. Quick Check:

   Access allowed only if session[:user_id] present [OK]

Hint: Redirect unless session[:user_id] exists to protect pages [OK]

Common Mistakes:

• Redirecting if session[:user_id] exists (wrong logic)
• Using wrong session key like :user
• Redirecting to wrong path on failure