title: Multiple Auth sessions in Laravel 4
body: <p>The project I'm currently working on is split up in an admin console and the normal frontend.
  Both front and backend are in the same Laravel instance.</p>
  
  <p>In the frontend I'm trying to create a user login system that works exclusively for the frontend. It uses a different table and model and it has different relations as oposed to the User model for the admin. </p>
  
  <p>What I can't figure out is a way to use the Laravel Auth class for both systems. Logically Auth uses one single config file, and more to the point, one session name. </p>
  
  <p>One solution that has been brought forward is not to use a different table and model and use some form of acl for the distinction. But I don't like the idea of mixing frontend and backend   in this way. Especially because it would mean I'd suddenly have to give the admin User model all the fields and relations previously unique to the frontend user. </p>
  
  <p>It just doesn't seem the right way to do things. I could switch to a different authentication system or seperate the admin into a package with its own configs but the scope of the project doesn't allow for such timeconsuming changes.</p>
  
  <p>I'd welcome any idea's you could provide. </p>