DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Your API Authentication Isn’t Broken; It’s Quietly Failing in These 6 Ways
  • The ID That Costs Millions: Why API Authorization Failures Keep Winning
  • Understanding Custom Authorization Mechanisms in Amazon API Gateway and AWS AppSync
  • Secrets in Code: Understanding Secret Detection and Its Blind Spots

Trending

  • AI Paradigm Shift: Analytics Without SQL
  • Build a GitHub Slack Bot With AWS Bedrock and MCP, Part 2
  • The Hidden Cost of AI Tokens: Engineering Patterns for 10x Resource Efficiency
  • Testing AI-Infused Apps: A Dual-Layer Framework for AI Quality Assurance
  1. DZone
  2. Data Engineering
  3. Databases
  4. Laravel Sanctum SPA API Authentication: Part 1

Laravel Sanctum SPA API Authentication: Part 1

Learn how to set up Laravel Sanctum authenticate single page applications (SPAs) that need to communicate with a Laravel powered API.

By 
Razet Jain user avatar
Razet Jain
·
Jan. 12, 21 · Tutorial
Likes (2)
Comment
Save
Tweet
Share
14.0K Views

Join the DZone community and get the full member experience.

Join For Free

Laravel Sanctum is a lightweight package to help make authentication in single-page or native mobile applications as easy as possible. Where before you had to choose between using the web middleware with sessions or an external package like Tymon's jwt-auth, you can now use Sanctum to accomplish both stateful and token-based authentication.

Installing Laravel Sanctum

First, let's actually install the package using Composer:

Shell
x
 
1
composer require laravel/sanctum

Then, we'll have to publish the migration files (and run the migration) with the following commands:

Shell
 




xxxxxxxxxx
1


 
1
php artisan vendor:publish --provider="Laravel\Sanctum\SanctumServiceProvider"
2
php artisan migrate


The last part of Sanctum's installation requires us modifying the app\Http\Kernel.php file to include a middleware that will inject Laravel's session cookie into our app's frontend. This is what will ultimately enable us to pass and retrieve data as an authenticated user:

PHP
 




xxxxxxxxxx
1


 
1
'api' => [
2
    EnsureFrontendRequestsAreStateful::class,
3
    'throttle:60,1'
4
]


CORS & Cookies

You should ensure that your application's CORS configuration is returning the Access-Control-Allow-Credentials header with a value of True by setting the supports_credentials option within your application's cors configuration file to true.

In addition, you should enable the withCredentials option on your global axios instance. Typically, this should be performed in your resources/js/bootstrap.js file:

JavaScript
xxxxxxxxxx
1
 
1
axios.defaults.withCredentials = true;

 Authenticating

To authenticate your SPA, your SPA's login page should first make a request to the /sanctum/csrf-cookie route to initialize CSRF protection for the application:

JavaScript
 




xxxxxxxxxx
1


 
1
axios.get('/sanctum/csrf-cookie').then(response => {
2
    // Login...
3
});


During this request Laravel will set an XSRF-TOKEN cookie containing the current CSRF token. This token should then be passed in an X-XSRF-TOKEN header on subsequent requests, which libraries like Axios and the Angular HttpClient will do automatically for you.

Protecting Routes

To protect routes so that all incoming requests must be authenticated, you should attach the sanctum authentication guard to your API routes within your routes/api.php file. 

PHP
 




xxxxxxxxxx
1


 
1
Route::middleware('auth:sanctum')->get('/user', function (Request $request) {
2
    return $request->user();
3
});


API Laravel authentication

Published at DZone with permission of Razet Jain. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Your API Authentication Isn’t Broken; It’s Quietly Failing in These 6 Ways
  • The ID That Costs Millions: Why API Authorization Failures Keep Winning
  • Understanding Custom Authorization Mechanisms in Amazon API Gateway and AWS AppSync
  • Secrets in Code: Understanding Secret Detection and Its Blind Spots

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook