These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
||
2 | |||
3 | return [ |
||
4 | |||
5 | /* |
||
6 | |-------------------------------------------------------------------------- |
||
7 | | Authentication Defaults |
||
8 | |-------------------------------------------------------------------------- |
||
9 | | |
||
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. |
||
13 | | |
||
14 | */ |
||
15 | |||
16 | 'defaults' => [ |
||
17 | 'guard' => 'web', |
||
18 | 'passwords' => '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 | | 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" |
||
35 | | |
||
36 | */ |
||
37 | |||
38 | 'guards' => [ |
||
39 | 'web' => [ |
||
40 | 'driver' => 'session', |
||
41 | 'provider' => 'users', |
||
42 | ], |
||
43 | |||
44 | 'api' => [ |
||
45 | 'driver' => 'token', |
||
46 | 'provider' => 'users', |
||
47 | ], |
||
48 | ], |
||
49 | |||
50 | /* |
||
51 | |-------------------------------------------------------------------------- |
||
52 | | User Providers |
||
53 | |-------------------------------------------------------------------------- |
||
54 | | |
||
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" |
||
64 | | |
||
65 | */ |
||
66 | |||
67 | 'providers' => [ |
||
68 | 'users' => [ |
||
69 | 'driver' => 'eloquent', |
||
70 | 'model' => App\User::class, |
||
71 | 'field' => 'username' // Adminlte laravel. Valid values: 'email' or 'username' |
||
72 | ], |
||
73 | |||
74 | // 'users' => [ |
||
0 ignored issues
–
show
|
|||
75 | // 'driver' => 'database', |
||
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
58% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them.
Loading history...
|
|||
76 | // 'table' => 'users', |
||
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
58% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them.
Loading history...
|
|||
77 | // 'field' => 'username' // Adminlte laravel. Valid values: 'email' or 'username' |
||
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
43% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them.
Loading history...
|
|||
78 | // ], |
||
79 | ], |
||
80 | |||
81 | /* |
||
82 | |-------------------------------------------------------------------------- |
||
83 | | Resetting Passwords |
||
84 | |-------------------------------------------------------------------------- |
||
85 | | |
||
86 | | You may specify multiple password reset configurations if you have more |
||
87 | | than one user table or model in the application and you want to have |
||
88 | | separate password reset settings based on the specific user types. |
||
89 | | |
||
90 | | The expire time is the number of minutes that the reset token should be |
||
91 | | considered valid. This security feature keeps tokens short-lived so |
||
92 | | they have less time to be guessed. You may change this as needed. |
||
93 | | |
||
94 | */ |
||
95 | |||
96 | 'passwords' => [ |
||
97 | 'users' => [ |
||
98 | 'provider' => 'users', |
||
99 | 'table' => 'password_resets', |
||
100 | 'expire' => 60, |
||
101 | ], |
||
102 | ], |
||
103 | |||
104 | ]; |
||
105 |
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.
The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.
This check looks for comments that seem to be mostly valid code and reports them.