Securing Laravel APIs with Sanctum or Passport Authentication
Jul 11, 2025 am 03:21 AMLaravel Sanctum and Laravel Passport are two tools for API authentication, suitable for different scenarios. 1. Sanctum is simpler and lighter, suitable for SPAs, mobile applications and basic token authentication; 2. Passport is a complete OAuth2 server that supports third-party access tokens, token revocation and fine-grained scope control. If you need the OAuth2 function, use Passport, otherwise Sanctum is more suitable. The settings process of the two are different: Sanctum needs to install, publish configuration, run migration, update user model and add middleware, and generate tokens through the createToken method; Passport needs to install, run migration, execute the passport:install command, update user model and register routes. When selecting, you should determine whether the advanced features of OAuth2 should be required based on the project requirements.
When building APIs with Laravel, securing them properly is cruel—especially if they're consumed by mobile apps or SPAs (Single Page Applications). Two common tools for this are Laravel Sanctum and Laravel Passport. Both can handle authentication, but they serve different use cases and have distinct setups.

Understanding the Differences: Sanctum vs. Passport
Laravel Sanctum and Passport both provide API authentication, but their approach is quite different.

- Sanctum is simpler and lightweight. It's great for SPAs, mobile apps, and simple token-based authentication.
- Passport is a full OAuth2 server, which means it supports more complex scenarios like third-party access tokens, token revocation, and granular scopes.
If you don't need full OAuth2 features, Sanctum is usually enough—and easier to set up.
Setting Up Sanctum in Your Laravel API
To secure your Laravel API with Sanctum, follow these steps:

Install Sanctum : Run
composer require laravel/sanctum
and publish the config file usingphp artisan vendor:publish --provider="Laravel\Sanctum\SanctumServiceProvider"
.Run Migrations : Sanctum needs a table to store tokens, so run
php artisan migrate
.Update User Model : Add the
HasApiTokens
trait to your User model (use Laravel\Sanctum\HasApiTokens;
).Configure Middleware : In
app/Http/Kernel.php
, make sure\Laravel\Sanctum\Http\Middleware\EnsureFrontendRequestsAreStateful::class
is added to theapi
middleware group.Create Tokens : Use
$user->createToken('token-name')
to generate tokens. Return that token to the client after login.Protect Routes : Use the
auth:sanctum
guard to protect your API routes.
One thing to note: Sanctum tokens don't expire by default. If you want short-lived tokens, enable that in the config and manage refresh logic on the client side.
How to Secure APIs Using Laravel Passport
If your app needs OAuth2 functionality (like allowing third-party services to authenticate), Passport is the better choice.
Here's how to get started:
- Install Passport : Run
composer require laravel/passport
and thenphp artisan migrate
. - Install JavaScript Dependencies : Run
npm install passport passport-http-bearer
if you're using Node.js for frontend. - Run Passport Install Command : Execute
php artisan passport:install
. This generates encryption keys and creates OAuth clients needed for issuing tokens. - Update User Model : Add the
HasApiTokens
trait from Passport and use theLaravel\Passport\HasApiTokens
namespace. - Add Passport Routes : In your
AuthServiceProvider
, callPassport::routes()
inside theboot
method. - Set Auth Guard : In
config/auth.php
, set theapi
driver topassport
.
With Passport, you can issue long-lived tokens, revoke them, and even allow users to grant access to third-party apps. However, this also adds complexity—so only go this route if you really need those features.
Choosing Between Sanctum and Passport
The decision really comes down to your project's requirements.
-
Go with Sanctum if:
- You're building a SPA or mobile app.
- You don't need OAuth2 features like scopes or third-party access.
- Simplicity and speed of setup matter.
-
Choose Passport if:
- You need full OAuth2 support.
- You're planning to offer an API for third-party developers.
- Token management beyond basic auth is required.
Both tools work well, but mixing them isn't recommended unless you have a very specific reason to do so.
Basically, start with Sanctum unless you know you'll need Passport's extra capabilities.
The above is the detailed content of Securing Laravel APIs with Sanctum or Passport Authentication. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

ToworkeffectivelywithpivottablesinLaravel,firstaccesspivotdatausingwithPivot()orwithTimestamps(),thenupdateentrieswithupdateExistingPivot(),managerelationshipsviadetach()andsync(),andusecustompivotmodelswhenneeded.1.UsewithPivot()toincludespecificcol

Laravelprovidesacleanandflexiblewaytosendnotificationsviamultiplechannelslikeemail,SMS,in-appalerts,andpushnotifications.Youdefinenotificationchannelsinthevia()methodofanotificationclass,andimplementspecificmethodsliketoMail(),toDatabase(),ortoVonage

Laravel performance optimization can improve application efficiency through four core directions. 1. Use the cache mechanism to reduce duplicate queries, store infrequently changing data through Cache::remember() and other methods to reduce database access frequency; 2. Optimize database from the model to query statements, avoid N 1 queries, specifying field queries, adding indexes, paging processing and reading and writing separation, and reduce bottlenecks; 3. Use time-consuming operations such as email sending and file exporting to queue asynchronous processing, use Supervisor to manage workers and set up retry mechanisms; 4. Use middleware and service providers reasonably to avoid complex logic and unnecessary initialization code, and delay loading of services to improve startup efficiency.

Methods to manage database state in Laravel tests include using RefreshDatabase, selective seeding of data, careful use of transactions, and manual cleaning if necessary. 1. Use RefreshDatabasetrait to automatically migrate the database structure to ensure that each test is based on a clean database; 2. Use specific seeds to fill the necessary data and generate dynamic data in combination with the model factory; 3. Use DatabaseTransactionstrait to roll back the test changes, but pay attention to its limitations; 4. Manually truncate the table or reseed the database when it cannot be automatically cleaned. These methods are flexibly selected according to the type of test and environment to ensure the reliability and efficiency of the test.

LaravelSanctum is suitable for simple, lightweight API certifications such as SPA or mobile applications, while Passport is suitable for scenarios where full OAuth2 functionality is required. 1. Sanctum provides token-based authentication, suitable for first-party clients; 2. Passport supports complex processes such as authorization codes and client credentials, suitable for third-party developers to access; 3. Sanctum installation and configuration are simpler and maintenance costs are low; 4. Passport functions are comprehensive but configuration is complex, suitable for platforms that require fine permission control. When selecting, you should determine whether the OAuth2 feature is required based on the project requirements.

Laravel simplifies database transaction processing with built-in support. 1. Use the DB::transaction() method to automatically commit or rollback operations to ensure data integrity; 2. Support nested transactions and implement them through savepoints, but it is usually recommended to use a single transaction wrapper to avoid complexity; 3. Provide manual control methods such as beginTransaction(), commit() and rollBack(), suitable for scenarios that require more flexible processing; 4. Best practices include keeping transactions short, only using them when necessary, testing failures, and recording rollback information. Rationally choosing transaction management methods can help improve application reliability and performance.

The core of handling HTTP requests and responses in Laravel is to master the acquisition of request data, response return and file upload. 1. When receiving request data, you can inject the Request instance through type prompts and use input() or magic methods to obtain fields, and combine validate() or form request classes for verification; 2. Return response supports strings, views, JSON, responses with status codes and headers and redirect operations; 3. When processing file uploads, you need to use the file() method and store() to store files. Before uploading, you should verify the file type and size, and the storage path can be saved to the database.

The most common way to generate a named route in Laravel is to use the route() helper function, which automatically matches the path based on the route name and handles parameter binding. 1. Pass the route name and parameters in the controller or view, such as route('user.profile',['id'=>1]); 2. When multiple parameters, you only need to pass the array, and the order does not affect the matching, such as route('user.post.show',['id'=>1,'postId'=>10]); 3. Links can be directly embedded in the Blade template, such as viewing information; 4. When optional parameters are not provided, they are not displayed, such as route('user.post',
