web-dev-qa-db-ja.com

Laravel認証ガード[]が定義されていないと言う

私は初心者で、laravelで学習とコードを開始します...ユーザーログインと登録を有効にするには、これを書きます（あるチュートリアルで見たように）：

routes.phpで

 Route::controllers([
     'auth'=>'Auth\AuthController',
     'password'=>'Auth\PasswordController', ]);

そして今、私が入力するとき： http：// localhost：8888/auth/login 私はエラーを取得します：

AuthManager.php行71のInvalidArgumentException：認証ガード[]が定義されていません。

enter image description here

また、viewフォルダーには、authディレクトリとlogin.blade.phpファイルなどはありません。

phplaravelauthenticationrouteslaravel-5.1
15
MonkeyBusiness

5.1.xから5.2にアップグレードした場合は、config/auth.phpが更新されていることを確認してください。

https://github.com/laravel/laravel/blob/v5.2.0/config/auth.php

18
Matt

config/auth.phpを編集した場合、たとえば別のガードを追加して設定をキャッシュするには、ガードがリロードされない場合があります。この問題が発生した場合、構成をクリアすると修正されます。

$php artisan config:clearまたは$php artisan config:cache

私はlaravel 5.5を使用しています

6
Jason Tumusiime

これは、config/auth.phpファイルの問題である可能性があります。ここでは、「デフォルト」配列がLaravel 5.2。

3
HoLiC

プログラムディレクトリApp/config/Auth.php

<?php
 return [
/*
|--------------------------------------------------------------------------
| Authentication Defaults
|--------------------------------------------------------------------------
|
| This option controls the default authentication "guard" and password
| reset options for your application. You may change these defaults
| as required, but they're a perfect start for most applications.
|
*/
'defaults' => [
    'guard' => 'web',
    'passwords' => '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: "session", "token"
|
*/
'guards' => [
    'web' => [
        'driver' => 'session',
        'provider' => 'users',
    ],
    'api' => [
        'driver' => 'token',
        'provider' => 'users',
    ],

   // define your Auth here..

   'your_auth_name' => [
        'driver' => 'session',
        'provider' => 'your table name',
    ],

],
/*
|--------------------------------------------------------------------------
| 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: "database", "eloquent"
|
*/
'providers' => [
    'users' => [
        'driver' => 'eloquent',
        'model' => App\User::class,
    ],
    // 'users' => [
    //     'driver' => 'database',
    //     'table' => 'users',
    // ],

    // add provider to your auth
       'table name' => [
        'driver' => 'eloquent',
        'model' => App\User::class,
    ],
   // **'model' => App\User::class,**
  // here App\User is model so you have to generate own model using **php artisan make:model Model_name**


],
/*
|--------------------------------------------------------------------------
| Resetting Passwords
|--------------------------------------------------------------------------
|
| Here you may set the options for resetting passwords including the view
| that is your password reset e-mail. You may also set the name of the
| table that maintains all of the reset tokens for your application.
|
| 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' => [
    'users' => [
        'provider' => 'users',
        'email' => 'auth.emails.password',
        'table' => 'password_resets',
        'expire' => 60,
    ],
], ];
0
sachinsuthariya