Custom user provider: User not set in session | Laravel | Page 1

vagrant jackal Jan 16, 2025, 7:20 PM

#

Good evening,

so I've implemented a custom user provider in one of our applications. Retrieving the data and works fine, dd'ing differnet points in the SessionGuard also seems to be working, the custom model is passed correctly everywhere. We use the database driver to store the sessions. For some reason tho, when the DatabaseSessionHandler receives the custom guard (which it does), the user is null. I've tried some debugging within the framework but I can't seem to figure out where the data is lost between the SessionGuard and DatabaseSessionHandler. I've also searched the internet finding similar problems but unfortunately no solutions.

Any help appreciated!

ocean flare Jan 16, 2025, 7:22 PM

#

Am I reading correctly that the only thing you'd want to change is the model? If that's the case, all you'd need to change is this https://github.com/laravel/laravel/blob/11.x/config/auth.php#L65

vagrant jackal Jan 16, 2025, 7:40 PM

#

No, the problem is that the user isnt saved to the session database 🙂

#

The actual user data comes from a rest api, which is not compatible with laravel's eloquent model. So I've implemented a custom user provider and guard to authenticate users using that api, but for some reason when the guard is passed to the DatabaseSessionHandler the user suddenly becomes null

#Custom user provider: User not set in session