hypothetical/config/auth.php

122 lines
4.1 KiB
PHP
Raw Normal View History

<?php
return [
/*
|--------------------------------------------------------------------------
2016-01-03 23:55:13 -05:00
| Authentication Defaults
|--------------------------------------------------------------------------
|
2024-03-19 17:11:58 -04:00
| This option defines the default authentication "guard" and password
| reset "broker" for your application. You may change these values
2016-01-03 23:55:13 -05:00
| as required, but they're a perfect start for most applications.
|
*/
2016-01-03 23:55:13 -05:00
'defaults' => [
2024-03-19 17:11:58 -04:00
'guard' => env('AUTH_GUARD', 'web'),
'passwords' => env('AUTH_PASSWORD_BROKER', 'users'),
2016-01-03 23:55:13 -05:00
],
/*
|--------------------------------------------------------------------------
2016-01-03 23:55:13 -05:00
| Authentication Guards
|--------------------------------------------------------------------------
|
2016-01-03 23:55:13 -05:00
| Next, you may define every authentication guard for your application.
| Of course, a great default configuration has been defined for you
2024-03-19 17:11:58 -04:00
| which utilizes session storage plus the Eloquent user provider.
2016-01-03 23:55:13 -05:00
|
2024-03-19 17:11:58 -04:00
| All authentication guards have a user provider, which defines how the
2016-01-03 23:55:13 -05:00
| users are actually retrieved out of your database or other storage
2024-03-19 17:11:58 -04:00
| system used by the application. Typically, Eloquent is utilized.
2016-01-03 23:55:13 -05:00
|
2022-05-23 21:01:33 -04:00
| Supported: "session"
|
*/
2016-01-03 23:55:13 -05:00
'guards' => [
'web' => [
'driver' => 'session',
'provider' => 'users',
],
2022-07-12 12:08:10 -04:00
'api' => [
'driver' => 'token',
'provider' => 'users',
'hash' => false
],
2016-01-03 23:55:13 -05:00
],
/*
|--------------------------------------------------------------------------
2016-01-03 23:55:13 -05:00
| User Providers
|--------------------------------------------------------------------------
|
2024-03-19 17:11:58 -04:00
| All authentication guards have a user provider, which defines how the
2016-01-03 23:55:13 -05:00
| users are actually retrieved out of your database or other storage
2024-03-19 17:11:58 -04:00
| system used by the application. Typically, Eloquent is utilized.
2016-01-03 23:55:13 -05:00
|
| If you have multiple user tables or models you may configure multiple
2024-03-19 17:11:58 -04:00
| providers to represent the model / table. These providers may then
2016-01-03 23:55:13 -05:00
| be assigned to any extra authentication guards you have defined.
|
| Supported: "database", "eloquent"
|
*/
2016-01-03 23:55:13 -05:00
'providers' => [
'users' => [
'driver' => 'eloquent',
2024-03-19 17:11:58 -04:00
'model' => env('AUTH_MODEL', App\Models\User::class),
2016-01-03 23:55:13 -05:00
],
// 'users' => [
// 'driver' => 'database',
// 'table' => 'users',
// ],
],
/*
|--------------------------------------------------------------------------
2016-01-03 23:55:13 -05:00
| Resetting Passwords
|--------------------------------------------------------------------------
|
2024-03-19 17:11:58 -04:00
| These configuration options specify the behavior of Laravel's password
| reset functionality, including the table utilized for token storage
| and the user provider that is invoked to actually retrieve users.
2016-01-03 23:55:13 -05:00
|
2023-03-13 17:33:19 -04:00
| The expiry time is the number of minutes that each reset token will be
| considered valid. This security feature keeps tokens short-lived so
| they have less time to be guessed. You may change this as needed.
|
2023-03-13 17:33:19 -04:00
| The throttle setting is the number of seconds a user must wait before
| generating more password reset tokens. This prevents the user from
| quickly generating a very large amount of password reset tokens.
|
*/
2016-01-03 23:55:13 -05:00
'passwords' => [
'users' => [
'provider' => 'users',
2024-03-19 17:11:58 -04:00
'table' => env('AUTH_PASSWORD_RESET_TOKEN_TABLE', 'password_reset_tokens'),
2016-01-03 23:55:13 -05:00
'expire' => 60,
2019-10-31 17:24:53 -04:00
'throttle' => 60,
2016-01-03 23:55:13 -05:00
],
],
2019-10-31 17:24:53 -04:00
/*
|--------------------------------------------------------------------------
| Password Confirmation Timeout
|--------------------------------------------------------------------------
|
| Here you may define the amount of seconds before a password confirmation
2024-03-19 17:11:58 -04:00
| window expires and users are asked to re-enter their password via the
2019-10-31 17:24:53 -04:00
| confirmation screen. By default, the timeout lasts for three hours.
|
*/
2024-03-19 17:11:58 -04:00
'password_timeout' => env('AUTH_PASSWORD_TIMEOUT', 10800),
2019-10-31 17:24:53 -04:00
];