Why authentication secures applications in Laravel - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to check if a user is logged in using Laravel's built-in authentication.

Laravel

<?php
if ([1]) {
    echo 'User is authenticated';
} else {
    echo 'User is not authenticated';
}

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

AUser::isLoggedIn()

Bauth()->guest()

CAuth::check()

DAuth::user()

Attempts:

3 left

💡 Hint

Common Mistakes

Using auth()->guest() which checks if user is NOT logged in.

Trying to call a method on User model directly.

In Laravel, Auth::check() returns true if the user is logged in.

2fill in blank

medium

Complete the code to protect a route so only authenticated users can access it.

Laravel

Route::get('/dashboard', function () {
    return view('dashboard');
})->[1]('auth');

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

Asecure

Bguard

CauthCheck

Dmiddleware

Attempts:

3 left

💡 Hint

Common Mistakes

Using guard which is for authentication drivers.

Using non-existent methods like authCheck or secure.

Laravel uses middleware('auth') to restrict routes to authenticated users.

3fill in blank

hard

Fix the error in the code to retrieve the authenticated user's email.

Laravel

<?php
$userEmail = [1]->email;
echo $userEmail;

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

AAuth::user()

BAuth::email()

CUser::email()

Dauth()->email

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to access email directly on auth() or Auth facade.

Using static calls on User model incorrectly.

Auth::user() returns the authenticated user object; then you access email.

4fill in blank

hard

Fill both blanks to create a middleware that redirects guests to login.

Laravel

<?php
public function handle($request, Closure $next)
{
    if ($request->user() [1] null) {
        return redirect()->route([2]);
    }
    return $next($request);
}

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

A==

B'login'

C!==

D'home'

Attempts:

3 left

💡 Hint

Common Mistakes

Using !== which checks for not equal, reversing logic.

Redirecting to 'home' instead of 'login'.

The middleware checks if user is null (not logged in) and redirects to the login route.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps user names to emails for authenticated users only.

Laravel

<?php
$users = User::all();
$result = [];
foreach ($users as $user) {
    if ($user->[1]()) {
        $result[$user->[2]] = $user->[3];
    }
}

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

AisAuthenticated

Bname

Cemail

DisActive

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent method isAuthenticated.

Mixing up keys and values in the array.

We check if user is active (authenticated users), then map name to email.

Practice

1. Why is authentication important in a Laravel application?

easy

A. It automatically fixes bugs in the code.

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

C. It speeds up the application performance.

D. It changes the application's design dynamically.

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 Laravel

   Laravel uses authentication to protect sensitive areas by verifying user identity, preventing unauthorized access.

3. Final Answer:

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

4. Quick Check:

   Authentication = Verify user identity [OK]

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

Common Mistakes:

• Confusing authentication with speeding up the app
• Thinking authentication fixes code bugs
• Believing authentication changes app design

2. Which Laravel feature is used to protect routes by requiring users to be logged in?

easy

A. Eloquent ORM

B. Route caching

C. Auth middleware

D. Blade templating

Solution

1. Step 1: Identify Laravel features related to authentication

   Laravel uses middleware to filter HTTP requests and control access to routes.

2. Step 2: Match the middleware that requires login

   The 'auth' middleware checks if a user is logged in before allowing access to a route.

3. Final Answer:

   Auth middleware -> Option C

4. Quick Check:

   Middleware 'auth' = Protect routes by login [OK]

Hint: Use 'auth' middleware to secure routes in Laravel [OK]

Common Mistakes:

• Confusing route caching with authentication
• Thinking Blade templates control access
• Mixing Eloquent ORM with authentication

3. What will happen if you try to access a route protected by auth middleware without logging in?

medium

A. You will be logged in automatically.

B. You will see the requested page content.

C. The application will crash with an error.

D. You will be redirected to the login page.

Solution

1. Step 1: Understand the behavior of 'auth' middleware

   The 'auth' middleware checks if a user is logged in; if not, it redirects to the login page.

2. Step 2: Predict the outcome of accessing protected route unauthenticated

   Since the user is not logged in, Laravel redirects them to the login page instead of showing content or crashing.

3. Final Answer:

   You will be redirected to the login page. -> Option D

4. Quick Check:

   Unauthenticated access + auth middleware = redirect to login [OK]

Hint: Unauthenticated users get sent to login page [OK]

Common Mistakes:

• Expecting the page content without login
• Thinking the app crashes on unauthorized access
• Assuming automatic login happens

4. Consider this route definition in Laravel:

Route::get('/dashboard', function () {
    return 'Dashboard';
})->middleware('auth');

What is wrong if users can access /dashboard without logging in?

medium

A. The 'auth' middleware is not registered or applied correctly.

B. The route URL is incorrect.

C. The return statement is missing.

D. Middleware should be named 'guest' instead of 'auth'.

Solution

1. Step 1: Analyze the route and middleware usage

   The route uses 'auth' middleware to restrict access to logged-in users only.

2. Step 2: Identify why unauthenticated users can access it

   If unauthenticated users access it, the middleware is either not applied properly or not registered in the kernel.

3. Final Answer:

   The 'auth' middleware is not registered or applied correctly. -> Option A

4. Quick Check:

   Middleware not working = unauthorized access [OK]

Hint: Check middleware registration if access is not restricted [OK]

Common Mistakes:

• Thinking route URL causes access issues
• Believing return statement affects authentication
• Confusing 'auth' with 'guest' middleware

5. You want to secure an admin panel in Laravel so only authenticated users with an 'admin' role can access it. Which approach best combines authentication and authorization?

hard

A. Use 'auth' middleware plus a custom middleware checking user role.

B. Use only 'auth' middleware without role checks.

C. Use 'guest' middleware to block logged-in users.

D. Use route caching to speed up access control.

Solution

1. Step 1: Understand authentication vs authorization

   Authentication checks if a user is logged in; authorization checks if they have permission (like 'admin' role).

2. Step 2: Combine middleware for both checks

   Use 'auth' middleware to ensure login, then add custom middleware to verify the 'admin' role for access control.

3. Final Answer:

   Use 'auth' middleware plus a custom middleware checking user role. -> Option A

4. Quick Check:

   Authentication + role check = secure admin access [OK]

Hint: Combine 'auth' and role-check middleware for secure admin [OK]

Common Mistakes:

• Using only 'auth' without role verification
• Using 'guest' middleware which blocks logged-in users
• Relying on route caching for security