sposchedule
119 строк · 4.0 Кб
1<?php
2
3return [
4
5/*
6|--------------------------------------------------------------------------
7| Authentication Defaults
8|--------------------------------------------------------------------------
9|
10| This option defines the default authentication "guard" and password
11| reset "broker" for your application. You may change these values
12| as required, but they're a perfect start for most applications.
13|
14*/
15
16'defaults' => [
17'guard' => env('AUTH_GUARD', 'web'),
18'passwords' => env('AUTH_PASSWORD_BROKER', 'users'),
19],
20
21/*
22|--------------------------------------------------------------------------
23| Authentication Guards
24|--------------------------------------------------------------------------
25|
26| Next, you may define every authentication guard for your application.
27| Of course, a great default configuration has been defined for you
28| which utilizes session storage plus the Eloquent user provider.
29|
30| All authentication guards have a user provider, which defines how the
31| users are actually retrieved out of your database or other storage
32| system used by the application. Typically, Eloquent is utilized.
33|
34| Supported: "session"
35|
36*/
37
38'guards' => [
39'web' => [
40'driver' => 'session',
41'provider' => 'users',
42],
43'api' => [
44'driver' => 'sanctum',
45'provider' => 'users',
46],
47],
48
49/*
50|--------------------------------------------------------------------------
51| User Providers
52|--------------------------------------------------------------------------
53|
54| All authentication guards have a user provider, which defines how the
55| users are actually retrieved out of your database or other storage
56| system used by the application. Typically, Eloquent is utilized.
57|
58| If you have multiple user tables or models you may configure multiple
59| providers to represent the model / table. These providers may then
60| be assigned to any extra authentication guards you have defined.
61|
62| Supported: "database", "eloquent"
63|
64*/
65
66'providers' => [
67'users' => [
68'driver' => 'eloquent',
69'model' => env('AUTH_MODEL', App\Models\User::class),
70],
71
72// 'users' => [
73// 'driver' => 'database',
74// 'table' => 'users',
75// ],
76],
77
78/*
79|--------------------------------------------------------------------------
80| Resetting Passwords
81|--------------------------------------------------------------------------
82|
83| These configuration options specify the behavior of Laravel's password
84| reset functionality, including the table utilized for token storage
85| and the user provider that is invoked to actually retrieve users.
86|
87| The expiry time is the number of minutes that each reset token will be
88| considered valid. This security feature keeps tokens short-lived so
89| they have less time to be guessed. You may change this as needed.
90|
91| The throttle setting is the number of seconds a user must wait before
92| generating more password reset tokens. This prevents the user from
93| quickly generating a very large amount of password reset tokens.
94|
95*/
96
97'passwords' => [
98'users' => [
99'provider' => 'users',
100'table' => env('AUTH_PASSWORD_RESET_TOKEN_TABLE', 'password_reset_tokens'),
101'expire' => 60,
102'throttle' => 60,
103],
104],
105
106/*
107|--------------------------------------------------------------------------
108| Password Confirmation Timeout
109|--------------------------------------------------------------------------
110|
111| Here you may define the amount of seconds before a password confirmation
112| window expires and users are asked to re-enter their password via the
113| confirmation screen. By default, the timeout lasts for three hours.
114|
115*/
116
117'password_timeout' => env('AUTH_PASSWORD_TIMEOUT', 10800),
118
119];