2018-10-04 19:10:43 +02:00
|
|
|
<?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' => [
|
2018-10-15 07:00:48 +02:00
|
|
|
'guard' => 'user',
|
2018-10-04 19:10:43 +02:00
|
|
|
'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' => [
|
2018-10-15 07:00:48 +02:00
|
|
|
'driver' => 'session',
|
2018-10-04 19:10:43 +02:00
|
|
|
'provider' => 'users',
|
|
|
|
],
|
2020-09-06 11:38:10 +02:00
|
|
|
|
2018-10-04 19:10:43 +02:00
|
|
|
'api' => [
|
2018-10-15 07:00:48 +02:00
|
|
|
'driver' => 'token',
|
|
|
|
'provider' => 'users',
|
2020-09-06 11:38:10 +02:00
|
|
|
'hash' => false,
|
2018-10-15 07:00:48 +02:00
|
|
|
],
|
2020-09-06 11:38:10 +02:00
|
|
|
|
2018-10-15 07:00:48 +02:00
|
|
|
'user' => [
|
|
|
|
'driver' => 'session',
|
2018-10-04 19:10:43 +02:00
|
|
|
'provider' => 'users',
|
|
|
|
],
|
2020-09-06 11:38:10 +02:00
|
|
|
|
2018-10-15 07:00:48 +02:00
|
|
|
'contact' => [
|
|
|
|
'driver' => 'session',
|
|
|
|
'provider' => 'contacts',
|
|
|
|
],
|
2022-06-03 01:27:36 +02:00
|
|
|
'vendor' => [
|
|
|
|
'driver' => 'session',
|
|
|
|
'provider' => 'vendors',
|
|
|
|
],
|
2018-10-04 19:10:43 +02:00
|
|
|
],
|
|
|
|
|
|
|
|
/*
|
|
|
|
|--------------------------------------------------------------------------
|
|
|
|
| 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' => [
|
2019-08-14 07:40:22 +02:00
|
|
|
'driver' => 'eloquent',
|
2018-10-15 07:00:48 +02:00
|
|
|
'model' => App\Models\User::class,
|
|
|
|
],
|
2020-09-06 11:38:10 +02:00
|
|
|
|
2018-10-15 07:00:48 +02:00
|
|
|
'contacts' => [
|
2019-08-14 07:40:22 +02:00
|
|
|
'driver' => 'eloquent',
|
2019-07-08 02:08:57 +02:00
|
|
|
'model' => App\Models\ClientContact::class,
|
2018-10-04 19:10:43 +02:00
|
|
|
],
|
2022-06-03 01:27:36 +02:00
|
|
|
'vendors' => [
|
|
|
|
'driver' => 'eloquent',
|
|
|
|
'model' => App\Models\VendorContact::class,
|
|
|
|
],
|
|
|
|
|
2018-10-04 19:10:43 +02:00
|
|
|
|
|
|
|
// 'users' => [
|
|
|
|
// 'driver' => 'database',
|
|
|
|
// 'table' => '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' => [
|
|
|
|
'users' => [
|
|
|
|
'provider' => 'users',
|
2018-10-15 07:00:48 +02:00
|
|
|
'table' => 'password_resets',
|
|
|
|
'expire' => 60,
|
2020-09-06 11:38:10 +02:00
|
|
|
'throttle' => 60,
|
2018-10-15 07:00:48 +02:00
|
|
|
],
|
2020-09-06 11:38:10 +02:00
|
|
|
|
2018-10-15 07:00:48 +02:00
|
|
|
'contacts' => [
|
|
|
|
'provider' => 'contacts',
|
|
|
|
'table' => 'password_resets',
|
|
|
|
'expire' => 60,
|
2018-10-04 19:10:43 +02:00
|
|
|
],
|
2022-06-03 01:27:36 +02:00
|
|
|
'vendors' => [
|
|
|
|
'provider' => 'vendors',
|
|
|
|
'table' => 'password_resets',
|
|
|
|
'expire' => 60,
|
|
|
|
],
|
2018-10-04 19:10:43 +02:00
|
|
|
],
|
|
|
|
|
2020-09-06 11:38:10 +02:00
|
|
|
/*
|
|
|
|
|--------------------------------------------------------------------------
|
|
|
|
| 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' => 10800,
|
|
|
|
|
2018-10-04 19:10:43 +02:00
|
|
|
];
|