title: Laravel 5.8 - Auth::user() with different guards
body: <p>Lets say I have the following guards:</p>
  
  <pre><code>  'guards' =&gt; [
      'web' =&gt; [
          'driver' =&gt; 'session',
          'provider' =&gt; 'users',
      ],
  
      'admin' =&gt; [
          'driver' =&gt; 'session',
          'provider' =&gt; 'users',
      ],
  ],
  </code></pre>
  
  <p>I login to my app as a normal user using the default 'web' guard and to access the authenticated user I can use the following:  <code>$user = Auth::user();</code></p>
  
  <pre><code>public function __construct()
  {
      $this-&gt;middleware('auth');
  
  }
  
  public function edit()
  {
      $user = Auth::user();
  
  
  }
  </code></pre>
  
  <p>At the same time I also login to the same app as an admin using the 'admin' guard and in admin controllers I have the following middleware and to access the authenticated admin I do the following: <code>Auth::guard('admin')-&gt;user()</code></p>
  
  <pre><code>public function __construct()
  {
      $this-&gt;middleware('auth:admin');
  
  }
  
  public function edit()
  {
      $user = Auth::guard('admin')-&gt;user();
  
  }
  </code></pre>
  
  <p>The question is do I need to specify the guard each time to access the admin user - I've noticed once I've authenticated in constructor using <code>$this-&gt;middleware('auth:admin')</code> I no longer need to specify the guard to access the authenticated user inside other controller methods? Is this correct behaviour</p>