Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
I’m using Jetstream for a user (client) portal and Filament for an admin (employee) portal. These are two separate entities.
I have already set up two guards (web and admin), but they both override the same session row in the database. As a result:
1. When I log out from one portal, it logs me out from both.
2. After logging into one portal, if I don’t refresh, I get a 419 expired error. If I refresh, everything works fine.
Question: Can I separate the sessions, for example, by using an admin_sessions table? Or am I doing something else wrong?
@devserge Unfortunately you’re going to need to create your own custom session guard class so that the session gets a unique name: https://github.com/laravel/framework/blob/b9cf7d3217732e9a0fa4f00e996b3f9cc5bf7abd/src/Illuminate/Auth/SessionGuard.php#L818-L826
perhaps if you had them on separate subdomains?
Thanks @martinbean and @snapey. The second suggestion is a lot easier for us, should've thought about that earlier. It works now by separating the filament portal on a subdomain. Thanks again.
Please or to participate in this conversation.