Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

dzc's avatar
Level 1

Where does Laravel store sessions with built-in auth?

I am using Laravel's built-in auth, and I have a few questions about how exactly it works. I am fairly new to Laravel and web dev so please bear with me.

  • IIUC the built-in auth uses session-based authentication. Where is the session data stored? The in-box Laravel migrations create a user``, personal_access_tokensandpassword_reset_tokenstables, but aside from theupdated_atcolumn of theusers` table, nothing gets updated on log-in.
  • What is the personal_access_tokens table used for? Is this meant to be used with something like Passport or Sanctum?
0 likes
2 replies
jlrdw's avatar

As in my other reply to your other post, I suggest start with the free training offered.

Also the documentation covers all these questions: https://laravel.com/docs/10.x/

What is the personal_access_tokens table used for?

See the chapter on laravel sanctum, it explains in detail.

Where does Laravel store sessions with built-in auth?

storage\framework\sessions

Snapey's avatar

Where is the session data stored

Depends what you have set for session storage

nothing gets updated on log-in

correct

What is the personal_access_tokens table used for

Passport or Sanctum and non cookie authenticated sessions.

Normally a session is started, a unique value as the session key, and then sends the session key to the client as a session cookie. When the client connects for the next request, it sends the cookie which Laravel decrypts and finds the session key and links the user to their session

Please or to participate in this conversation.