Appearance
Laravel Passport Integration
This guide will show Laravel API authentication using passport
Introduction
Laravel Passport provides a full OAuth2 server implementation for your Laravel application in a matter of minutes. Passport is built on top of the League OAuth2 server that is maintained by Andy Millington and Simon Hamp.
Passport Or Sanctum?
Before getting started, you may wish to determine if your application would be better served by Laravel Passport or Laravel sanctum. If your application absolutely needs to support OAuth2, then you should use Laravel Passport.
However, if you are attempting to authenticate a single-page application, mobile application, or issue API tokens, you should use Laravel sanctum. Laravel Sanctum does not support OAuth2; however, it provides a much simpler API authentication development experience.
Installation
To get started, install Passport via the Composer package manager:
bashcomposer require laravel/passport
Passport's service provider registers its own database migration directory, so you should migrate your database after installing the package. The Passport migrations will create the tables your application needs to store OAuth2 clients and access tokens:
bashphp artisan migrate
Next, you should execute the
passport:install
Artisan command. This command will create the encryption keys needed to generate secure access tokens. In addition, the command will create "personal access" and "password grant" clients which will be used to generate access tokens:bashphp artisan passport:install
Note
If you would like to use UUIDs as the primary key value of the Passport
Client
model instead of auto-incrementing integers, please install Passport using the uuids option.After running the
passport:install
command, add theLaravel\Passport\HasApiTokens
trait to yourApp\Models\User
model. This trait will provide a few helper methods to your model which allow you to inspect the authenticated user's token and scopes:php<?php namespace App\Models; use Illuminate\Database\Eloquent\Factories\HasFactory; use Illuminate\Foundation\Auth\User as Authenticatable; use Illuminate\Notifications\Notifiable; use Laravel\Passport\HasApiTokens; class User extends Authenticatable { use HasApiTokens, HasFactory, Notifiable; }
Finally, in your application's
config/auth.php
configuration file, you should set thedriver
option of theapi
authentication guard topassport
. This will instruct your application to use Passport'sTokenGuard
when authenticating incoming API requests:php'guards' => [ 'web' => [ 'driver' => 'session', 'provider' => 'users', ], 'api' => [ 'driver' => 'passport', 'provider' => 'users', ], ],
Client UUIDs
You may also run the passport:install
command with the --uuids
option present. This option will instruct Passport that you would like to use UUIDs instead of auto-incrementing integers as the Passport Client
model's primary key values. After running the passport:install
command with the --uuids
option, you will be given additional instructions regarding disabling Passport's default migrations:
bash
php artisan passport:install --uuids
Deploying Passport
When deploying Passport to your application's servers for the first time, you will likely need to run the passport:keys
command. This command generates the encryption keys Passport needs in order to generate access tokens. The generated keys are not typically kept in source control:
bash
php artisan passport:keys
If necessary, you may define the path where Passport's keys should be loaded from. You may use the Passport::loadKeysFrom
method to accomplish this. Typically, this method should be called from the boot
method of your application's App\Providers\AuthServiceProvider
class:
php
/**
* Register any authentication / authorization services.
*
* @return void
*/
public function boot()
{
$this->registerPolicies();
Passport::routes();
Passport::loadKeysFrom(__DIR__.'/../secrets/oauth');
}
Note
You can read Laravel Passport documentation in detail for Configurations, Migration, Upgrading Passport, Issuing Access Tokens, Requesting Tokens, Refreshing, Revoking & Purging Tokens etc..