[ 'guard' => 'web', 'passwords' => 'mst_customer', ], /* |-------------------------------------------------------------------------- | 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' => 'mst_customer', ], 'api' => [ 'driver' => 'token', 'provider' => 'mst_customer', 'hash' => false, ], 'admin' => [ 'driver' => 'session', 'provider' => 'admin', ], 'mst_customer' => [ 'driver' => 'session', 'provider' => 'mst_customer', ], ], /* |-------------------------------------------------------------------------- | User Providers |-------------------------------------------------------------------------- | | All authentication drivers have a user provider. This defines how the | mst_customer 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' => [ 'mst_customer' => [ 'driver' => 'eloquent', 'model' => App\Customer::class, ], 'admin' => [ 'driver' => 'eloquent', 'model' => App\Admin::class, ] // 'mst_customer' => [ // 'driver' => 'database', // 'table' => 'mst_customer', // ], ], /* |-------------------------------------------------------------------------- | 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' => [ 'mst_customer' => [ 'provider' => 'mst_customer', 'table' => 'password_resets', 'expire' => 60, ], 'admin' => [ 'provider' => 'admin', 'table' => 'password_resets', 'expire' => 60, ], ], ];