Laravel 5.4 Multi auth - Auth::guard()->user() empty

Question

I've created a multi auth test in Laravel 5.4. It's using custom middlewares, custom Eloquent providers, etc. The auth flow is working, I can login in both ways. But if the user is signed in, in the home controller when I want to check the user with Auth::user() or Auth::guard()->user(), it's empty. The Auth::guard() is empty as well. But I don't understand, why?! It should contains the signed in user instance, shouldn't it?

Also the $request->getUserResolver() says that the guard is null... o.O

What did I do wrong?

Here it is my test repo, if you want to check my code.

Thank you in advance!

Edit 1:

In the \app\Http\Controllers\Employee\HomeController.php the Auth::guard()->user() and the Auth::user() are empty.

namespace App\Http\Controllers\Employee;

use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
use Illuminate\Support\Facades\Auth;

class HomeController extends Controller
{

    public function __construct(Request $request)
    {
        $this->middleware('auth.employee:employee');
    }

    public function index(Request $request)
    {
        $users[] = Auth::user();
        $users[] = Auth::guard()->user();
        $users[] = Auth::guard('employee')->user();

        dd($users);

        return view('employees.home.index');
    }
}

Last time I saw a post with a person just putting a link to their GitHub repo, GitHub was down for about an hour and the question got downvoted. True story. — apokryfos
– apokryfos, Commented Feb 3, 2017 at 16:46
@Chay22 Do you want me to explain all steps (with code snipets) in my question how I implemented the multi auth? — Sas Sam
– Sas Sam, Commented Feb 3, 2017 at 16:52
That's a good idea. Anyways, how about adding an 's' Auth::guard('employees')->user(); And before jumping into that you have to make sure that your guard is reach out login method inside the Illuminate\Auth\SessionGuard class to populate the session. What I mean was how'd you authenticate the user at the first place? — Chay22
– Chay22, Commented Feb 3, 2017 at 16:58
Lurking into your repo, I think the issue comes from the way you register provider Auth::provider('eloquent.employee' ...) you filled out with the driver name which should be Auth::provider('employees' ...) And, doesn't it need to be loaded just before AuthServiceProvider resolved, like registering the provider inside AppServiceProvider instead? Dunno... — Chay22
– Chay22, Commented Feb 3, 2017 at 17:09

Ganesh K · Accepted Answer · 2018-02-27 02:39:26Z

4

Auth::shouldUse(your_guard_name);
call this in your login function

edited Feb 27, 2018 at 2:39

answered Apr 2, 2017 at 8:53

Ganesh K

66010 silver badges18 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Mirdrack Over a year ago

This also can be called in the constructor of the controller that is going to use the guard

Ankit Jain · Accepted Answer · 2017-02-04 04:42:56Z

0

Change the driver name in the config/auth.php as..

'employees' => [
        'driver' => 'eloquent',
        'model' => App\Models\UserEmployee::class,
    ],
    'customers' => [
        'driver' => 'eloquent',
        'model' => App\Models\Customer::class,
    ],

answered Feb 4, 2017 at 4:42

Ankit Jain

1,0468 silver badges13 bronze badges

1 Comment

Sas Sam Over a year ago

Why should I do that? That's my custom driver with custom conditions for auth.

Collectives™ on Stack Overflow

Laravel 5.4 Multi auth - Auth::guard()->user() empty

2 Answers 2

1 Comment

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related