Why authentication secures applications in Ruby on Rails - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add user authentication in a Rails controller.

Ruby on Rails

before_action :[1], only: [:edit, :update, :destroy]

Drag options to blanks, or click blank then click option'

Aauthenticate_user!

Bverify_token

Ccheck_admin

Dauthorize_user

Attempts:

3 left

💡 Hint

Common Mistakes

Using authorization methods instead of authentication

Forgetting the exclamation mark in method name

The authenticate_user! method ensures only logged-in users can access certain actions.

2fill in blank

medium

Complete the code to create a secure login form in Rails.

Ruby on Rails

<%= form_with url: session_path, method: :post do |[1]| %>

Drag options to blanks, or click blank then click option'

Af

Bbuilder

Cform

Dsession

Attempts:

3 left

💡 Hint

Common Mistakes

Using variable names that are not standard form builders

Using plural or unrelated variable names

The variable f is commonly used as the form builder in Rails forms.

3fill in blank

hard

Fix the error in the authentication check method.

Ruby on Rails

def current_user
  @current_user ||= User.find_by(id: session[:[1]])
end

Drag options to blanks, or click blank then click option'

Aid

Bcurrent_user_id

Cuser_id

Dsession_id

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'id' instead of 'user_id'

Using 'session_id' which is unrelated

The session stores the user_id to identify the logged-in user.

4fill in blank

hard

Fill both blanks to securely log out a user in a Rails controller.

Ruby on Rails

def destroy
  session[:[1]] = [2]
  redirect_to root_path
end

Drag options to blanks, or click blank then click option'

Auser_id

Bnil

Cfalse

Dcurrent_user

Attempts:

3 left

💡 Hint

Common Mistakes

Setting session key to false instead of nil

Using wrong session key name

Setting session[:user_id] to nil logs out the user by clearing their session.

5fill in blank

hard

Fill all three blanks to create a secure user authentication helper method.

Ruby on Rails

def logged_in?
  !!session[:[1]] && User.exists?(id: session[:[2]]) && @current_user = User.find_by(id: session[:[3]])
end

Drag options to blanks, or click blank then click option'

Auser_id

Dcurrent_user_id

Attempts:

3 left

💡 Hint

Common Mistakes

Using different keys for session lookup

Using 'current_user_id' which is not standard

All session references must use user_id to check and find the logged-in user.

Practice

1. Why is authentication important in a Rails application?

easy

A. It automatically fixes bugs in the code.

B. It speeds up the application loading time.

C. It verifies the identity of users before granting access.

D. It changes the application's design theme.

Solution

1. Step 1: Understand the purpose of authentication

   Authentication is the process of checking who a user is before allowing access to certain parts of an application.

2. Step 2: Identify the correct role of authentication in Rails

   In Rails, authentication protects private data and user accounts by verifying user identity.

3. Final Answer:

   It verifies the identity of users before granting access. -> Option C

4. Quick Check:

   Authentication = Verify identity [OK]

Hint: Authentication means checking who you are before access [OK]

Common Mistakes:

• Confusing authentication with performance optimization
• Thinking authentication changes app design
• Believing authentication fixes code bugs automatically

2. Which of the following is the correct way to add Devise authentication to a Rails model named User?

easy

A. Add before_action :authenticate_user! in the User model.

B. Add authenticate :user in the routes file.

C. Add has_secure_password in the User controller.

D. Add devise :database_authenticatable, :registerable inside the User model.

Solution

1. Step 1: Identify how Devise is used in models

   Devise requires adding devise with modules inside the model class to enable authentication features.

2. Step 2: Check each option's correctness

   Add devise :database_authenticatable, :registerable inside the User model correctly shows adding devise :database_authenticatable, :registerable inside the User model. Other options misuse syntax or place code in wrong files.

3. Final Answer:

   Add devise :database_authenticatable, :registerable inside the User model. -> Option D

4. Quick Check:

   Devise modules go inside model class [OK]

Hint: Devise modules go inside model class, not routes or controller [OK]

Common Mistakes:

• Placing authentication code in routes or controllers incorrectly
• Using has_secure_password instead of Devise syntax
• Calling authenticate_user! in model instead of controller

3. Given this Rails controller code using Devise:

class DashboardController < ApplicationController
  before_action :authenticate_user!

  def index
    render plain: "Welcome, #{current_user.email}!"
  end
end

What will happen if an unauthenticated user tries to access /dashboard?

medium

A. They will be redirected to the sign-in page.

B. They will see the welcome message with their email.

C. They will get a 404 Not Found error.

D. They will see a blank page.

Solution

1. Step 1: Understand before_action :authenticate_user! behavior

   This method checks if a user is signed in; if not, it redirects to the sign-in page.

2. Step 2: Predict the controller response for unauthenticated user

   Since the user is not signed in, the controller will redirect them to the login page instead of showing the welcome message.

3. Final Answer:

   They will be redirected to the sign-in page. -> Option A

4. Quick Check:

   Unauthenticated user = redirect to sign-in [OK]

Hint: authenticate_user! redirects unauthenticated users to login [OK]

Common Mistakes:

• Assuming unauthenticated users see content
• Thinking it returns 404 error
• Expecting a blank page instead of redirect

4. You added before_action :authenticate_user! in your Rails controller, but unauthenticated users can still access protected pages. What is the most likely cause?

medium

A. You did not add devise_for :users in routes.rb.

B. You placed before_action after the action methods.

C. You did not restart the Rails server after adding authentication.

D. You forgot to include Devise in your Gemfile.

Solution

1. Step 1: Check the role of devise_for :users in routes

   This line sets up all necessary routes for Devise authentication, including sign-in and sign-out paths.

2. Step 2: Understand impact of missing routes

   If devise_for :users is missing, authentication paths do not exist, so authenticate_user! cannot redirect unauthenticated users properly.

3. Final Answer:

   You did not add devise_for :users in routes.rb. -> Option A

4. Quick Check:

   Missing devise routes = no authentication redirects [OK]

Hint: Devise needs routes set with devise_for :users [OK]

Common Mistakes:

• Assuming server restart fixes missing routes
• Placing before_action incorrectly does not bypass it
• Forgetting to add Devise gem causes errors, not silent failure

5. You want to secure an API endpoint in Rails so only authenticated users can access it. You use Devise and add before_action :authenticate_user! in your API controller. However, API clients get redirected to the sign-in page instead of receiving an error. How can you fix this to return a 401 Unauthorized status instead?

hard

A. Add skip_before_action :authenticate_user! in the API controller.

B. Override Devise's authenticate_user! to respond with JSON and 401 status for API requests.

C. Remove before_action :authenticate_user! and check authentication manually.

D. Change the API controller to inherit from ApplicationController instead of ActionController::API.

Solution

1. Step 1: Understand default Devise behavior for unauthenticated users

   Devise redirects unauthenticated users to sign-in page by default, which is not suitable for APIs.

2. Step 2: Customize authentication failure response for API

   Override the failure response to return JSON with 401 Unauthorized status when API requests fail authentication.

3. Final Answer:

   Override Devise's authenticate_user! to respond with JSON and 401 status for API requests. -> Option B

4. Quick Check:

   API auth failure = JSON 401, not redirect [OK]

Hint: API needs JSON 401 response, not redirect [OK]

Common Mistakes:

• Removing authentication check loses security
• Skipping before_action disables protection
• Changing controller inheritance does not fix response format