mirror of
https://github.com/snipe/snipe-it.git
synced 2024-12-26 22:19:41 -08:00
296de34e8a
I'm going ahead and merging this, since the upgrade doesn't break Flysystem any worse than the current develop is broken, so far as I can tell. * Upgraded framework to Laravel 6 ### TO DO: - Fix password restriction rules- the old library isn’t compatible with Laravel 6 :( - Figure out why in-app API calls are returning “Unauthorized” * More updates from Input:: to Request:: helper * Switch to Request:: from Input * Added passport config * Fixed goofy password minimum in seeder * Added laravel/helpers * Changed ($item) to ($item->id) in forms I have no idea why this is necessary * Changed ($item) to ($item->id) in forms * Updated API middleware to auth:api * Updated with added laravel auth.php values * FIxed *&!^$%^&$^%!!!! ajax issue * Switch to Request::get from Input::get * Switched to Request facade * Added password security minimums back in The package we were using has not been updated to Laravel v6, so I created custom validators instead * Added language strings for error messages for password rules * Fixed `($item)` issue in formActions for partials
124 lines
4 KiB
PHP
124 lines
4 KiB
PHP
<?php
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| DO NOT EDIT THIS FILE DIRECTLY.
|
|
|--------------------------------------------------------------------------
|
|
| This file reads from your .env configuration file and should not
|
|
| be modified directly.
|
|
*/
|
|
|
|
|
|
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' => [
|
|
'guard' => 'web',
|
|
'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' => [
|
|
'driver' => 'session',
|
|
'provider' => 'users',
|
|
],
|
|
|
|
'api' => [
|
|
'driver' => 'passport',
|
|
'provider' => 'users',
|
|
'hash' => false,
|
|
],
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| 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' => [
|
|
'driver' => 'eloquent',
|
|
'model' => App\Models\User::class,
|
|
],
|
|
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| 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',
|
|
'email' => 'auth.emails.password',
|
|
'table' => 'password_resets',
|
|
'expire' => env('LOGIN_LOCKOUT_DURATION', 60),
|
|
'throttle' => env('LOGIN_MAX_ATTEMPTS', 60),
|
|
],
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| 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,
|
|
|
|
];
|