I want to take advantage of the new policy system in 5.1.11, but it seems like Laravel's auth user is heavily baked into it.
I have a legacy system that I'm running in parallel with Laravel 5, and that system uses its own auth + sessions system. At present I'm not using any Laravel 5 auth, but I am wrapping the legacy member table with an Eloquent model. I've built my own simple auth loader based on queries from the legacy system tables.
All I want is for the presence of a legacy session or auth cookie, to set that legacy member model as being logged in.
What's the easiest way to achieve this?