|
4 | 4 |
|
5 | 5 | /* |
6 | 6 | |-------------------------------------------------------------------------- |
7 | | - | Default Authentication Driver |
| 7 | + | Authentication Defaults |
8 | 8 | |-------------------------------------------------------------------------- |
9 | 9 | | |
10 | | - | This option controls the authentication driver that will be utilized. |
11 | | - | This driver manages the retrieval and authentication of the users |
12 | | - | attempting to get access to protected areas of your application. |
13 | | - | |
14 | | - | Supported: "database", "eloquent" |
| 10 | + | This option controls the default authentication "guard" and password |
| 11 | + | reset options for your application. You may change these defaults |
| 12 | + | as required, but they're a perfect start for most applications. |
15 | 13 | | |
16 | 14 | */ |
17 | 15 |
|
18 | | - 'driver' => 'eloquent', |
| 16 | + 'defaults' => [ |
| 17 | + 'guard' => 'web', |
| 18 | + 'passwords' => 'users', |
| 19 | + ], |
19 | 20 |
|
20 | 21 | /* |
21 | 22 | |-------------------------------------------------------------------------- |
22 | | - | Authentication Model |
| 23 | + | Authentication Guards |
23 | 24 | |-------------------------------------------------------------------------- |
24 | 25 | | |
25 | | - | When using the "Eloquent" authentication driver, we need to know which |
26 | | - | Eloquent model should be used to retrieve your users. Of course, it |
27 | | - | is often just the "User" model but you may use whatever you like. |
| 26 | + | Next, you may define every authentication guard for your application. |
| 27 | + | Of course, a great default configuration has been defined for you |
| 28 | + | here which uses session storage and the Eloquent user provider. |
| 29 | + | |
| 30 | + | All authentication drivers have a user provider. This defines how the |
| 31 | + | users are actually retrieved out of your database or other storage |
| 32 | + | mechanisms used by this application to persist your user's data. |
| 33 | + | |
| 34 | + | Supported: "session", "token" |
28 | 35 | | |
29 | 36 | */ |
30 | 37 |
|
31 | | - 'model' => Pterodactyl\Models\User::class, |
| 38 | + 'guards' => [ |
| 39 | + 'web' => [ |
| 40 | + 'driver' => 'session', |
| 41 | + 'provider' => 'users', |
| 42 | + ], |
| 43 | + |
| 44 | + 'api' => [ |
| 45 | + 'driver' => 'token', |
| 46 | + 'provider' => 'users', |
| 47 | + ], |
| 48 | + ], |
32 | 49 |
|
33 | 50 | /* |
34 | 51 | |-------------------------------------------------------------------------- |
35 | | - | Authentication Table |
| 52 | + | User Providers |
36 | 53 | |-------------------------------------------------------------------------- |
37 | 54 | | |
38 | | - | When using the "Database" authentication driver, we need to know which |
39 | | - | table should be used to retrieve your users. We have chosen a basic |
40 | | - | default value but you may easily change it to any table you like. |
| 55 | + | All authentication drivers have a user provider. This defines how the |
| 56 | + | users are actually retrieved out of your database or other storage |
| 57 | + | mechanisms used by this application to persist your user's data. |
| 58 | + | |
| 59 | + | If you have multiple user tables or models you may configure multiple |
| 60 | + | sources which represent each model / table. These sources may then |
| 61 | + | be assigned to any extra authentication guards you have defined. |
| 62 | + | |
| 63 | + | Supported: "database", "eloquent" |
41 | 64 | | |
42 | 65 | */ |
43 | 66 |
|
44 | | - 'table' => 'users', |
| 67 | + 'providers' => [ |
| 68 | + 'users' => [ |
| 69 | + 'driver' => 'eloquent', |
| 70 | + 'model' => Pterodactyl\Models\User::class, |
| 71 | + ], |
| 72 | + |
| 73 | + // 'users' => [ |
| 74 | + // 'driver' => 'database', |
| 75 | + // 'table' => 'users', |
| 76 | + // ], |
| 77 | + ], |
45 | 78 |
|
46 | 79 | /* |
47 | 80 | |-------------------------------------------------------------------------- |
48 | | - | Password Reset Settings |
| 81 | + | Resetting Passwords |
49 | 82 | |-------------------------------------------------------------------------- |
50 | 83 | | |
51 | 84 | | Here you may set the options for resetting passwords including the view |
52 | | - | that is your password reset e-mail. You can also set the name of the |
| 85 | + | that is your password reset e-mail. You may also set the name of the |
53 | 86 | | table that maintains all of the reset tokens for your application. |
54 | 87 | | |
| 88 | + | You may specify multiple password reset configurations if you have more |
| 89 | + | than one user table or model in the application and you want to have |
| 90 | + | separate password reset settings based on the specific user types. |
| 91 | + | |
55 | 92 | | The expire time is the number of minutes that the reset token should be |
56 | 93 | | considered valid. This security feature keeps tokens short-lived so |
57 | 94 | | they have less time to be guessed. You may change this as needed. |
58 | 95 | | |
59 | 96 | */ |
60 | 97 |
|
61 | | - 'password' => [ |
62 | | - 'email' => 'emails.password', |
63 | | - 'table' => 'password_resets', |
64 | | - 'expire' => 60, |
| 98 | + 'passwords' => [ |
| 99 | + 'users' => [ |
| 100 | + 'provider' => 'users', |
| 101 | + 'email' => 'emails.password', |
| 102 | + 'table' => 'password_resets', |
| 103 | + 'expire' => 60, |
| 104 | + ], |
65 | 105 | ], |
66 | 106 |
|
67 | 107 | ]; |
0 commit comments