Upgrade & Secure Your Future with DevOps, SRE, DevSecOps, MLOps!

We spend hours scrolling social media and waste money on things we forget, but won’t spend 30 minutes a day earning certifications that can change our lives.
Master in DevOps, SRE, DevSecOps & MLOps by DevOps School!

Learn from Guru Rajesh Kumar and double your salary in just one year.


Get Started Now!

File in Laravel config/auth.php ‘guards’ Configuration

The ‘guards’ array allows you to define multiple guards, each representing a different way to authenticate users. By default, Laravel provides two guards: ‘web’ and ‘api’.

web‘ Guard: The ‘web’ guard is used for authenticating users using session-based authentication. It is commonly used for web applications where users authenticate via a login form and the session is maintained throughout their browsing session. This guard uses Laravel’s default session driver for managing user sessions.

api‘ Guard: The ‘api’ guard is used for authenticating API requests using token-based authentication. It is typically used for stateless APIs where clients authenticate by sending an API token with each request. The ‘api’ guard uses token-based authentication mechanisms like JSON Web Tokens (JWT) or API tokens generated by Laravel’s Passport package.

You can also define custom guards in the ‘guards’ array according to your application’s requirements. For example, you might create a ‘admin’ guard to authenticate administrators separately from regular users.

Here’s an example configuration of the ‘guards’ array in config/auth.php:

‘guards’ => [ ‘web’ => [ ‘driver’ => ‘session’, ‘provider’ => ‘users’, ], ‘api’ => [ ‘driver’ => ‘token’, ‘provider’ => ‘users’, ], // Custom Guard ‘admin’ => [ ‘driver’ => ‘session’, ‘provider’ => ‘admins’, ], ],

Multiple Guards Example

‘guards’ => [ ‘web’ => [ ‘driver’ => ‘session’, ‘provider’ => ‘users’, ], ‘api’ => [ ‘driver’ => ‘token’, ‘provider’ => ‘api_users’, ], ‘admin’ => [ ‘driver’ => ‘session’, ‘provider’ => ‘admin_users’, ], ],

In this example, we have defined three guards:

‘web’: Uses the session driver and retrieves users from the ‘users’ provider.

‘api’: Uses the token driver and retrieves users from the ‘api_users’ provider.

‘admin’: Uses the session driver and retrieves users from the ‘admin_users’ provider.

Utilizing Guards in Laravel: Once you have defined multiple guards, you can utilize them in your application by specifying the guard name when performing authentication checks or specifying the guard in routes, controllers, or middleware.

if (Auth::guard(‘web’)->check()) { // User is authenticated using the ‘web’ guard } else { // User is not authenticated }

Route Middleware Example:

Route::group([‘middleware’ => ‘auth:api’], function () { // Routes that require authentication using the ‘api’ guard });

Related Posts

Fixing the “Could not find PHP executable” Error in Live Server on VS Code

this is a common issue and easy to fix! This guide will walk you through the step-by-step solution to get your PHP files running in the browser….

How to Fix the “npm.ps1 cannot be loaded” Error on Windows When Running npm start

If you’re a developer working with React or any Node.js-based projects, you may have encountered the following error when trying to run npm start in PowerShell on…

Simplify Database Migrations with kitloong/laravel-migrations-generator in Laravel

Laravel provides a powerful migration system that allows developers to easily define and manage database schema changes. However, when working with legacy databases or large projects, manually…

Understanding and Fixing the “Unable to Read Key from File” Error in Laravel Passport

Laravel Passport is a powerful package for handling OAuth2 authentication in Laravel applications. It allows you to authenticate API requests with secure access tokens. However, like any…

How to Generate a GitHub OAuth Token with Read/Write Permissions for Private Repositories

When working with GitHub, you may need to interact with private repositories. For that, GitHub uses OAuth tokens to authenticate and authorize your access to these repositories….

Laravel Error: Target class [DatabaseSeeder] does not exist – Solved for Laravel 10+

If you’re working with Laravel 10+ and run into the frustrating error: …you’re not alone. This is a common issue developers face, especially when upgrading from older…

0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x