Loading…
Eloquent, routing, middleware, queues and the service container.
In a Laravel app, what is the difference between authentication and authorization? Give one example of each from a typical blog where users write posts.
A teammate saves new users with 'password' => $request->password
straight into the database. What is wrong with that, and how should
you store and later check a password in Laravel?
Inside a controller you need the current user. What do
Auth::user(), Auth::id() (or auth()->id()) and Auth::check()
each return, and what do you get from them when nobody is logged in?
You are writing a custom login controller. What does
Auth::attempt(['email' => $email, 'password' => $password]) do step
by step, and what does it return?
You start a new Laravel project that needs registration, login, password reset and email verification. What are Laravel's authentication starter kits, such as Breeze, Jetstream and Fortify, and why would you use one instead of writing these screens yourself?
Your logout route only calls Auth::logout() and redirects home.
What else should a logout action in a session-based Laravel app do,
and why?