Login and logout flow in Ruby on Rails - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens after a successful login in a Rails app?

Consider a typical Rails login controller action that authenticates a user and sets a session. What is the expected behavior immediately after a successful login?

Ruby on Rails

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

A The user ID is stored in the session and the browser is redirected to the dashboard page.

B The user ID is stored in a cookie and the login form is re-rendered.

C The user ID is stored in a global variable and the user is redirected to the login page.

D The user ID is stored in the session and the login form is re-rendered with an error.

💡 Hint

Think about what happens when login is successful: where is the user ID stored and what does the app do next?

On successful login, Rails stores the user ID in the session hash and redirects the user to a protected page like the dashboard. This keeps the user logged in across requests.

❓ state_output

intermediate

What is the session state after logout?

Given this logout action in a Rails controller, what will be the state of session[:user_id] after it runs?

Ruby on Rails

def destroy
  session.delete(:user_id)
  redirect_to root_path
end

A session[:user_id] will be set to false.

B session[:user_id] will be nil or undefined.

C session[:user_id] will still hold the user ID.

D session[:user_id] will raise an error if accessed.

💡 Hint

Deleting a key from the session removes it. What does that mean when you try to read it later?

Calling session.delete(:user_id) removes the key from the session hash, so accessing session[:user_id] returns nil.

📝 Syntax

advanced

Identify the syntax error in this login method

Which option contains the correct syntax for authenticating a user in Rails?

Ruby on Rails

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

A if user.authenticate(params[:password])

B if user | user.authenticate(params[:password])

C if user && user.authenticate(params[:password])

D if user&.authenticate(params[:password])

💡 Hint

Consider what happens if user is nil. How to safely call authenticate?

Using the safe navigation operator &. prevents calling authenticate on nil, avoiding a NoMethodError.

🔧 Debug

advanced

Why does this logout action fail to clear the session?

Given this logout method, why does the user remain logged in after logout?

Ruby on Rails

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

A Because <code>redirect_to</code> must come before session changes.

B Because <code>session.clear</code> is required to clear the session.

C Because <code>session[:user_id] == nil</code> is a comparison, not an assignment.

D Because the session key must be set to false, not nil.

💡 Hint

Look carefully at the line that tries to clear the session key. Is it doing what you expect?

The code uses == which compares values but does not assign. To clear the session key, use = nil or session.delete(:user_id).

🧠 Conceptual

expert

What is the main security benefit of resetting the session on logout?

In Rails, calling reset_session during logout is recommended. Why is this important?

A It prevents session fixation attacks by generating a new session ID.

B It logs the user out from all devices automatically.

C It encrypts the session data to protect user information.

D It speeds up the logout process by clearing cookies faster.

💡 Hint

Think about what happens if an attacker steals a session ID before logout.

Resetting the session creates a new session ID, preventing attackers from reusing an old session ID (session fixation). This improves security.

Practice

1. What does the session[:user_id] typically store in a Rails login flow?

easy

A. The user's email address

B. The ID of the logged-in user

C. The user's password

D. The current time of login

Solution

1. Step 1: Understand session usage in Rails login

   In Rails, session[:user_id] is used to store the unique identifier of the logged-in user to keep track of their session.

2. Step 2: Differentiate from other user data

   Passwords and emails are not stored in session for security and privacy reasons; only the user ID is stored.

3. Final Answer:

   The ID of the logged-in user -> Option B

4. Quick Check:

   session[:user_id] = user ID [OK]

Hint: Session stores user ID, not password or email [OK]

Common Mistakes:

• Thinking session stores password
• Confusing session with cookies
• Assuming session stores full user object

2. Which of the following is the correct way to clear the user session during logout in a Rails controller?

easy

A. reset_session

B. session.clear

C. session[:user_id] = nil

D. session.delete(:user_id)

Solution

1. Step 1: Identify Rails method to reset session

   The reset_session method clears the entire session safely and is the recommended way to log out a user.

2. Step 2: Compare with other options

   While session.delete(:user_id) or setting it to nil removes the user ID, reset_session is more secure as it resets the whole session.

3. Final Answer:

   reset_session -> Option A

4. Quick Check:

   Use reset_session to clear all session data [OK]

Hint: Use reset_session to fully clear session on logout [OK]

Common Mistakes:

• Only deleting user_id but leaving other session data
• Using session.clear, which doesn't regenerate the session ID
• Setting session[:user_id] to nil without resetting session

3. Given this Rails controller code for login:

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

What happens if the password is incorrect?

medium

A. User is redirected to dashboard

B. User ID is saved in session

C. Application crashes with error

D. Login form is re-rendered with alert

Solution

1. Step 1: Analyze the if condition

   The condition user&.authenticate(params[:password]) returns false if password is wrong, so the else block runs.

2. Step 2: Understand else block behavior

   The else block sets a flash alert and re-renders the login form with render :new.

3. Final Answer:

   Login form is re-rendered with alert -> Option D

4. Quick Check:

   Wrong password triggers else block [OK]

Hint: Wrong password triggers else block with alert [OK]

Common Mistakes:

• Assuming redirect happens on wrong password
• Thinking session is set even if password fails
• Believing app crashes on wrong password

4. Identify the error in this logout action:

def destroy
  session[:user_id] = nil
  redirect_to login_path
end

What is the main issue with this logout method?

medium

A. It does not clear the entire session

B. It redirects to the wrong path

C. It raises a syntax error

D. It does not delete the user record

Solution

1. Step 1: Check session clearing method

   Setting session[:user_id] = nil only removes the user ID but leaves other session data intact.

2. Step 2: Understand best practice for logout

   Best practice is to use reset_session to clear all session data and prevent session fixation attacks.

3. Final Answer:

   It does not clear the entire session -> Option A

4. Quick Check:

   Partial session clearing is insecure [OK]

Hint: Partial session clearing leaves data behind; use reset_session [OK]

Common Mistakes:

• Thinking setting user_id to nil clears session fully
• Ignoring session fixation security risks
• Assuming redirect path affects logout correctness

5. You want to ensure users cannot access the dashboard without logging in. Which code snippet correctly enforces this in a Rails controller using the login session?

hard

A. before_action :require_login

def require_login
redirect_to login_path if session[:user_id].present?
end

B. before_action :require_login

def require_login
redirect_to dashboard_path if session[:user_id].nil?
end

C. before_action :require_login

def require_login
redirect_to login_path unless session[:user_id]
end

D. before_action :require_login

def require_login
redirect_to login_path if session[:user_id] == true
end

Solution

1. Step 1: Understand login check logic

   Users should be redirected to login if session[:user_id] is missing (nil or false).

2. Step 2: Analyze each option's condition

   before_action :require_login def require_login redirect_to login_path unless session[:user_id] end redirects to login unless user_id exists, correctly blocking access. Others have incorrect conditions or redirect to wrong paths.

3. Final Answer:

   before_action :require_login with redirect unless session[:user_id] -> Option C

4. Quick Check:

   Redirect to login if no user_id [OK]

Hint: Redirect unless session[:user_id] exists to block access [OK]

Common Mistakes:

• Using wrong condition logic for session check
• Redirecting to dashboard instead of login
• Checking session[:user_id] == true which is incorrect