Login, Register & Logout Flows

Auth Flow Code

// Registration flow
public function store(Request $request)
{
    $request->validate([
        'name' => 'required|string|max:255',
        'email' => 'required|email|unique:users',
        'password' => ['required', 'confirmed', Rules\Password::defaults()],
    ]);

    $user = User::create([
        'name' => $request->name,
        'email' => $request->email,
        'password' => Hash::make($request->password),
    ]);

    event(new Registered($user));
    Auth::login($user);
    return redirect(route('dashboard'));
}

// Login flow
public function store(LoginRequest $request)
{
    $request->authenticate(); // Validates + rate limits
    $request->session()->regenerate(); // Prevent session fixation
    return redirect()->intended(route('dashboard'));
}

// Logout
public function destroy(Request $request)
{
    Auth::guard('web')->logout();
    $request->session()->invalidate();
    $request->session()->regenerateToken();
    return redirect('/');
}

// Using Auth in controllers/views
$user = Auth::user();           // Current user
$id = Auth::id();               // Current user ID
if (Auth::check()) { }          // Is logged in?
@auth ... @endauth              // Blade directive

Industry Best Practices

• Always write tests for this functionality - it's the most reliable way to catch regressions when you refactor or update packages
• Document your implementation decisions in code comments, especially when you deviate from Laravel conventions - future team members (including yourself) will thank you
• Follow the single responsibility principle: each class does one thing. If a method grows beyond 20 lines, consider extracting helper methods or moving logic to a service class
• Profile performance with Laravel Debugbar (composer require barryvdh/laravel-debugbar) during development - it shows query counts, memory usage, and timeline for every request
• Keep dependencies up to date: run composer audit regularly to check for security vulnerabilities in your package dependencies

Industry Best Practices

• Always write tests for this functionality - it's the most reliable way to catch regressions when you refactor or update packages
• Document your implementation decisions in code comments, especially when you deviate from Laravel conventions - future team members (including yourself) will thank you
• Follow the single responsibility principle: each class does one thing. If a method grows beyond 20 lines, consider extracting helper methods or moving logic to a service class
• Profile performance with Laravel Debugbar (composer require barryvdh/laravel-debugbar) during development - it shows query counts, memory usage, and timeline for every request
• Keep dependencies up to date: run composer audit regularly to check for security vulnerabilities in your package dependencies

Industry Best Practices

• Always write tests for this functionality - it's the most reliable way to catch regressions when you refactor or update packages
• Document your implementation decisions in code comments, especially when you deviate from Laravel conventions - future team members (including yourself) will thank you
• Follow the single responsibility principle: each class does one thing. If a method grows beyond 20 lines, consider extracting helper methods or moving logic to a service class
• Profile performance with Laravel Debugbar (composer require barryvdh/laravel-debugbar) during development - it shows query counts, memory usage, and timeline for every request
• Keep dependencies up to date: run composer audit regularly to check for security vulnerabilities in your package dependencies

Tip

Practice Task

Quick Quiz

Common Mistake