Registration flow in Laravel - Mini Project: Build & Apply

Registration flow

📖 Scenario: You are building a simple user registration flow for a website using Laravel. Users will enter their name, email, and password to create an account.

🎯 Goal: Create a Laravel registration flow that stores user data securely and validates input.

📋 What You'll Learn

Create a User model with name, email, and password fields

Add a configuration variable for minimum password length

Write a controller method to validate and save user registration data

Complete the registration route and view to handle user input

💡 Why This Matters

🌍 Real World

User registration is a fundamental feature for websites and apps that require user accounts.

💼 Career

Understanding how to build secure registration flows is essential for backend and full-stack developers working with Laravel.

1

Create the User model

Create a Laravel model called User with the fields name, email, and password in the migration file.

Laravel

// Create User model and migration with name, email, and password fields
// Your code here

Hint

Use php artisan make:model User -m to create the model and migration. Then add the fields in the migration file.

2

Add password length configuration

Add a configuration variable called MIN_PASSWORD_LENGTH in config/auth.php and set it to 8.

Laravel

<?php

// Add MIN_PASSWORD_LENGTH = 8 in config/auth.php
// Your code here

Hint

Open config/auth.php and add the new key-value pair inside the returned array.

3

Create registration controller method

In app/Http/Controllers/Auth/RegisterController.php, write a method called register that validates name, email, and password from the request. Use the MIN_PASSWORD_LENGTH config for password minimum length. Hash the password and save the new User.

Laravel

<?php

namespace App\Http\Controllers\Auth;

use App\Http\Controllers\Controller;
use App\Models\User;
use Illuminate\Http\Request;
use Illuminate\Support\Facades\Hash;
use Illuminate\Support\Facades\Config;

class RegisterController extends Controller
{
    // Your code here
}

Hint

Use Laravel's validate method on the request and Hash::make to encrypt the password before saving.

4

Add registration route and view

Add a POST route /register in routes/web.php that uses RegisterController@register. Create a Blade view resources/views/register.blade.php with a form that has name, email, and password inputs and submits to /register.

Laravel

<?php

// Add POST route for /register
// Your code here

// Create Blade view with form
// Your code here

Hint

Define the route in routes/web.php and create a Blade template with a form that uses POST and includes CSRF protection.

Practice

1. What is the main purpose of the registration flow in a Laravel application?

easy

A. To collect and save new user information securely

B. To display user profiles

C. To delete user accounts

D. To update existing user passwords

Solution

1. Step 1: Understand registration flow purpose

   The registration flow is designed to gather new user data and store it safely.

2. Step 2: Compare options with purpose

   Only To collect and save new user information securely matches the goal of collecting and saving new user info securely.

3. Final Answer:

   To collect and save new user information securely -> Option A

4. Quick Check:

   Registration flow = Collect and save user info [OK]

Hint: Registration means new user data collection and storage [OK]

Common Mistakes:

• Confusing registration with profile display
• Thinking registration deletes users
• Mixing registration with password update

2. Which Laravel method is used to securely hash a user's password during registration?

easy

A. Hash::make()

B. User::hashPassword()

C. bcrypt_password()

D. password_hash()

Solution

1. Step 1: Identify Laravel's password hashing method

   Laravel uses the Hash facade with the make() method to hash passwords securely.

2. Step 2: Verify options

   Only Hash::make() is the correct Laravel method; others are incorrect or not Laravel-specific.

3. Final Answer:

   Hash::make() -> Option A

4. Quick Check:

   Laravel password hashing = Hash::make() [OK]

Hint: Use Hash::make() to hash passwords in Laravel [OK]

Common Mistakes:

• Using non-Laravel functions for hashing
• Calling methods that don't exist in Laravel
• Confusing bcrypt_password() with Laravel's method

3. Given this Laravel controller code snippet for registration:

public function register(Request $request) {
  $validated = $request->validate([
    'email' => 'required|email|unique:users',
    'password' => 'required|min:8'
  ]);
  User::create([
    'email' => $validated['email'],
    'password' => Hash::make($validated['password'])
  ]);
  return redirect('/welcome');
}

What happens if the email already exists in the users table?

medium

A. The user is created with duplicate email

B. Validation fails and an error message is shown

C. The password is hashed twice

D. The app crashes with a database error

Solution

1. Step 1: Understand validation rules

   The 'unique:users' rule prevents duplicate emails by validating against the users table.

2. Step 2: Effect of validation failure

   If the email exists, validation fails and Laravel automatically returns an error message to the user.

3. Final Answer:

   Validation fails and an error message is shown -> Option B

4. Quick Check:

   Unique email validation = error on duplicate [OK]

Hint: unique:users stops duplicate emails during validation [OK]

Common Mistakes:

• Assuming duplicate users are created
• Thinking password hashes twice
• Expecting a crash instead of validation error

4. Identify the error in this Laravel registration code:

public function register(Request $request) {
  $data = $request->validate([
    'email' => 'required|email',
    'password' => 'required|min:8'
  ]);
  User::create([
    'email' => $data['email'],
    'password' => $data['password']
  ]);
  return redirect('/home');
}

medium

A. Validation rules are incorrect

B. Redirect URL is invalid

C. Missing password hashing before saving

D. Request object is not injected

Solution

1. Step 1: Check password handling

   The password is saved directly without hashing, which is insecure and incorrect.

2. Step 2: Confirm validation and redirect

   Validation rules and redirect URL are valid; request injection is correct.

3. Final Answer:

   Missing password hashing before saving -> Option C

4. Quick Check:

   Password must be hashed before saving [OK]

Hint: Always hash passwords before saving to database [OK]

Common Mistakes:

• Saving plain text passwords
• Ignoring validation rules
• Incorrect redirect paths

5. You want to customize the Laravel registration flow to send a welcome email after successful registration. Which is the best way to implement this?

hard

A. Add email sending code directly after User::create() in the controller

B. Override the User model's save() method to send email

C. Send the email from the registration form view

D. Use Laravel events to listen for user registration and send email

Solution

1. Step 1: Understand Laravel best practices

   Using events decouples email sending from registration logic, improving maintainability.

2. Step 2: Evaluate options

   Directly sending email in the controller mixes concerns; overriding the User model's save() method is risky; sending the email from the registration form view breaks MVC pattern.

3. Final Answer:

   Use Laravel events to listen for user registration and send email -> Option D

4. Quick Check:

   Events handle post-registration tasks cleanly [OK]

Hint: Use events for post-registration actions like emails [OK]

Common Mistakes:

• Mixing email logic in controller
• Modifying model save() for side effects
• Placing logic in views