title: Class App\Http\Middleware\Authenticate:api does not exist on Broadcasting
body: <p>I am having an issue with the auth:api guard working with broadcasting.</p>
  <p>I get the error <code>Class App\Http\Middleware\Authenticate:api does not exist</code> if I call <code>php artisan route:list</code>.</p>
  <p>BroadcastServiceProvider.php:</p>
  <pre><code>&lt;?php
  
  namespace App\Providers;
  
  use Illuminate\Support\Facades\Broadcast;
  use Illuminate\Support\ServiceProvider;
  
  class BroadcastServiceProvider extends ServiceProvider
  {
      /**
       * Bootstrap any application services.
       *
       * @return void
       */
      public function boot()
      {
          Broadcast::routes([
              'prefix' =&gt; 'api',
              'middleware' =&gt; 'auth:api',
          ]);
  
          require base_path('routes/channels.php');
      }
  }
  </code></pre>
  <p>config/auth.php:</p>
  <pre><code>&lt;?php
  
  return [
  
      /*
      |--------------------------------------------------------------------------
      | Authentication Defaults
      |--------------------------------------------------------------------------
      |
      | This option controls the default authentication &quot;guard&quot; and password
      | reset options for your application. You may change these defaults
      | as required, but they're a perfect start for most applications.
      |
      */
  
      'defaults' =&gt; [
          'guard' =&gt; 'web',
          'passwords' =&gt; 'users',
      ],
  
      /*
      |--------------------------------------------------------------------------
      | Authentication Guards
      |--------------------------------------------------------------------------
      |
      | Next, you may define every authentication guard for your application.
      | Of course, a great default configuration has been defined for you
      | here which uses session storage and the Eloquent user provider.
      |
      | All authentication drivers have a user provider. This defines how the
      | users are actually retrieved out of your database or other storage
      | mechanisms used by this application to persist your user's data.
      |
      | Supported: &quot;session&quot;, &quot;token&quot;
      |
      */
  
      'guards' =&gt; [
          'web' =&gt; [
              'driver' =&gt; 'session',
              'provider' =&gt; 'users',
          ],
  
          'api' =&gt; [
              'driver' =&gt; 'passport',
              'provider' =&gt; 'users',
              'hash' =&gt; false,
          ],
      ],
  
      /*
      |--------------------------------------------------------------------------
      | User Providers
      |--------------------------------------------------------------------------
      |
      | All authentication drivers have a user provider. This defines how the
      | users are actually retrieved out of your database or other storage
      | mechanisms used by this application to persist your user's data.
      |
      | If you have multiple user tables or models you may configure multiple
      | sources which represent each model / table. These sources may then
      | be assigned to any extra authentication guards you have defined.
      |
      | Supported: &quot;database&quot;, &quot;eloquent&quot;
      |
      */
  
      'providers' =&gt; [
          'users' =&gt; [
              'driver' =&gt; 'eloquent',
              'model' =&gt; App\User::class,
          ],
  
          // 'users' =&gt; [
          //     'driver' =&gt; 'database',
          //     'table' =&gt; 'users',
          // ],
      ],
  
      /*
      |--------------------------------------------------------------------------
      | Resetting Passwords
      |--------------------------------------------------------------------------
      |
      | You may specify multiple password reset configurations if you have more
      | than one user table or model in the application and you want to have
      | separate password reset settings based on the specific user types.
      |
      | The expire time is the number of minutes that the reset token should be
      | considered valid. This security feature keeps tokens short-lived so
      | they have less time to be guessed. You may change this as needed.
      |
      */
  
      'passwords' =&gt; [
          'users' =&gt; [
              'provider' =&gt; 'users',
              'table' =&gt; 'password_resets',
              'expire' =&gt; 60,
              'throttle' =&gt; 60,
          ],
      ],
  
      /*
      |--------------------------------------------------------------------------
      | Password Confirmation Timeout
      |--------------------------------------------------------------------------
      |
      | Here you may define the amount of seconds before a password confirmation
      | times out and the user is prompted to re-enter their password via the
      | confirmation screen. By default, the timeout lasts for three hours.
      |
      */
  
      'password_timeout' =&gt; 10800,
  
  ];
  </code></pre>
  <p>If I remove the middleware from the BroadcastingServiceProvider for the Broadcast::routes I no longer have the issue.</p>
  <p>I am using this same guard <code>auth:api</code> in my routes file as well, which seems to be working fine:</p>
  <pre><code>Route::group(['middleware' =&gt; 'auth:api'], function () {
  
  });
  </code></pre>
  <p>I thought perhaps the imports in the <code>providers</code> array in config/app.php was the problem, but that doesn't seem to be it. Any thoughts?</p>