Laravel 9 Multiple Authentication Example using Guard
Hello Artisan,
In this laravel 9 multiple authentication tutorial, I will show you how to create multiple authentication example in Laravel 9 using custom guard. You know that Laravel provides guard to create multiple authentications for multiple tables.
So in this tutorial, i will simply create multiple authentication in laravel 9 natively for admins users login. You will learn how to use guard to create multiple login system in Laravel with multiple tables. You will also learn laravel 9 multi auth with different tables from this laravel 9 multiple auth tutorial.
I will create a custom guard to create laravel 9 multiple authentication using guard tutorial. If you don't know how to create custom guard, how create multiple login mechanism using that custom guard then this tutorial is going to be a perfect example for you.
Let's start this Laravel 9 multiple authentication tutorial.
Step 1: Create Model
To create this multiple auth tutorial using guard, we need a model. To create a model and update it like below:
php artisan make:model Doctor -m
And update it like:
App\Model\Doctor.php
namespace App\Models;
use Illuminate\Support\Facades\Hash;
use Illuminate\Database\Eloquent\Model;
use Illuminate\Notifications\Notifiable;
use Illuminate\Database\Eloquent\Factories\HasFactory;
use Illuminate\Foundation\Auth\User as Authenticatable;
class Doctor extends Authenticatable
{
use HasFactory, Notifiable;
protected $guarded = [];
public function setPasswordAttribute($value)
{
$this->attributes['password'] = Hash::make($value);
}
public function scopeIsActive($query)
{
return $query->where('is_active',1);
}
}
And in the migrations file, paste this below code.
public function up()
{
Schema::create('doctors', function (Blueprint $table) {
$table->id();
$table->string('name');
$table->string('email',32)->unique();
$table->string('password',255);
$table->boolean('is_active')->default(true);
$table->timestamps();
});
}
Step 2 : Setup or Create Custom Guard
In this step, we need to create our custom guard name. So visit config/auth.php and create your own guard name as many as you want.
config/auth.php
return [
/*
|--------------------------------------------------------------------------
| Authentication Defaults
|--------------------------------------------------------------------------
|
| This option controls the default authentication "guard" and password
| reset options for your application. You may change these defaults
| as required, but they're a perfect start for most applications.
|
*/
'defaults' => [
'guard' => 'web',
'passwords' => 'users',
],
/*
|--------------------------------------------------------------------------
| Authentication Guards
|--------------------------------------------------------------------------
|
| Next, you may define every authentication guard for your application.
| Of course, a great default configuration has been defined for you
| here which uses session storage and the Eloquent user provider.
|
| All authentication drivers have a user provider. This defines how the
| users are actually retrieved out of your database or other storage
| mechanisms used by this application to persist your user's data.
|
| Supported: "session", "token"
|
*/
'guards' => [
'web' => [
'driver' => 'session',
'provider' => 'users',
],
'doctor' => [
'driver' => 'session',
'provider' => 'doctors',
],
'api' => [
'driver' => 'token',
'provider' => 'users',
'hash' => false,
],
],
/*
|--------------------------------------------------------------------------
| User Providers
|--------------------------------------------------------------------------
|
| All authentication drivers have a user provider. This defines how the
| users are actually retrieved out of your database or other storage
| mechanisms used by this application to persist your user's data.
|
| If you have multiple user tables or models you may configure multiple
| sources which represent each model / table. These sources may then
| be assigned to any extra authentication guards you have defined.
|
| Supported: "database", "eloquent"
|
*/
'providers' => [
'users' => [
'driver' => 'eloquent',
'model' => App\Models\User::class,
],
'doctors' => [
'driver' => 'eloquent',
'model' => App\Models\Doctor::class,
],
// 'users' => [
// 'driver' => 'database',
// 'table' => 'users',
// ],
],
/*
|--------------------------------------------------------------------------
| Resetting Passwords
|--------------------------------------------------------------------------
|
| You may specify multiple password reset configurations if you have more
| than one user table or model in the application and you want to have
| separate password reset settings based on the specific user types.
|
| The expire time is the number of minutes that the reset token should be
| considered valid. This security feature keeps tokens short-lived so
| they have less time to be guessed. You may change this as needed.
|
*/
'passwords' => [
'users' => [
'provider' => 'users',
'table' => 'password_resets',
'expire' => 60,
'throttle' => 60,
],
'doctors' => [
'provider' => 'doctors',
'table' => 'password_resets',
'expire' => 60,
'throttle' => 60,
],
],
/*
|--------------------------------------------------------------------------
| Password Confirmation Timeout
|--------------------------------------------------------------------------
|
| Here you may define the amount of seconds before a password confirmation
| times out and the user is prompted to re-enter their password via the
| confirmation screen. By default, the timeout lasts for three hours.
|
*/
'password_timeout' => 10800,
];
Step 3: Create Route
Now in this step, we have to create our route for creating Laravel multi auth using guard. Let's create our route.
routes/doctor.php
use Illuminate\Support\Facades\Auth;
use Illuminate\Support\Facades\Route;
use App\Http\Controllers\Doctor\Auth\LoginController;
Route::name('doctor.')->namespace('Doctor')->prefix('doctor')->group(function(){
Route::namespace('Auth')->middleware('guest:doctor')->group(function(){
//login route
Route::get('/login','LoginController@login')->name('login');
Route::post('/login','LoginController@processLogin');
});
Route::namespace('Auth')->middleware('auth:doctor')->group(function(){
Route::post('/logout',function(){
Auth::guard('doctor')->logout();
return redirect()->action([
LoginController::class,
'login'
]);
})->name('logout');
});
});
Now we have to define our custom route path from the route service provider. So change it like below.
app\Providers\RouteServiceProvider.php
namespace App\Providers;
use Illuminate\Cache\RateLimiting\Limit;
use Illuminate\Foundation\Support\Providers\RouteServiceProvider as ServiceProvider;
use Illuminate\Http\Request;
use Illuminate\Support\Facades\RateLimiter;
use Illuminate\Support\Facades\Route;
class RouteServiceProvider extends ServiceProvider
{
public const HOME = '/home';
public const DOCTOR = '/doctor/home';
protected $namespace = 'App\\Http\\Controllers';
public function boot()
{
$this->configureRateLimiting();
$this->routes(function () {
Route::prefix('api')
->middleware('api')
->namespace($this->namespace)
->group(base_path('routes/api.php'));
Route::middleware('web')
->namespace($this->namespace)
->group(base_path('routes/web.php'));
//our custom route path
Route::middleware('web')
->namespace($this->namespace)
->group(base_path('routes/doctor.php'));
});
}
protected function configureRateLimiting()
{
RateLimiter::for('api', function (Request $request) {
return Limit::perMinute(60)->by(optional($request->user())->id ?: $request->ip());
});
}
}
Step 4: Create Controller
Now in this step, you have to create our login controller and method which are defined in the doctor.php route. So let's create that method.
App\Http\Controllers\Doctor\Auth\LoginController.php
namespace App\Http\Controllers\Doctor\Auth;
use Illuminate\Http\Request;
use Facades\App\Helper\Helper;
use App\Http\Requests\LoginRequest;
use App\Http\Controllers\Controller;
use App\Models\Doctor;
use Illuminate\Support\Facades\Auth;
use Illuminate\Support\Facades\View;
use App\Providers\RouteServiceProvider;
use Symfony\Component\HttpFoundation\Response;
class LoginController extends Controller
{
public function login()
{
if(View::exists('doctor.auth.login'))
{
return view('doctor.auth.login');
}
abort(Response::HTTP_NOT_FOUND);
}
public function processLogin(Request $request)
{
$credentials = $request->except(['_token']);
if(isDoctorActive($request->email))
{
if(Auth::guard('doctor')->attempt($credentials))
{
return redirect(RouteServiceProvider::DOCTOR);
}
return redirect()->action([
LoginController::class,
'login'
])->with('message','Credentials not matced in our records!');
}
return redirect()->action([
LoginController::class,
'login'
])->with('message','You are not an active doctors!');
}
}
Now paste this into your helper.php file.
app\helper.php
use App\Models\Doctor;
if(!function_exists('isDoctorActive'))
{
function isDoctorActive($email) : bool
{
$doctor = Doctor::whereEmail($email)->isActive()->exists();
return $doctor ? true : false;
}
}
Now almost all are set to. We have to just create our blade view.
Step 5: Create Blade
Now just paste this HTML code in the following path to create a multiple login systems in Laravel using custom guard.
resources/views/doctor/auth/login.blade.php
for logout, use this route and form
Recommended: Laravel 9 Role Based Authentication Tutorial
Hope you have understood this example tutorial. You can create as many guards as you want from config/auth.php and have to make a login system using those custom guards. You can use the User model or you can use another model. It doesn't matter.
