/home/techb158/ileadtechnology.com/SSM/config
NameSizeModeActions
activitylog.php15240644editdlrm
app.php95480644editdlrm
auth.php37640644editdlrm
broadcasting.php16010644editdlrm
cache.php31760644editdlrm
config.php230644editdlrm
cors.php8290644editdlrm
data.php210644editdlrm
database.php50710644editdlrm
debugbar.php79740644editdlrm
default.php210644editdlrm
excel.php63980644editdlrm
filesystems.php26400644editdlrm
hasing.php15700644editdlrm
jwt.php100070644editdlrm
logging.php28950644editdlrm
mail.php46890644editdlrm
nexmo.php9890644editdlrm
paypal.php7590644editdlrm
permission.php28480644editdlrm
purifier.php47200644editdlrm
queue.php27160644editdlrm
sentry.php3650644editdlrm
services.php9490644editdlrm
session.php69710644editdlrm
system.php230644editdlrm
telescope.php53590644editdlrm
twilio.php13980644editdlrm
view.php15640644editdlrm
Edit: /home/techb158/ileadtechnology.com/SSM/config/auth.php (3764B)
[ 'guard' => 'api', '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' => 'jwt', 'provider' => 'users', ], ], /* |-------------------------------------------------------------------------- | 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\User::class, ], // 'users' => [ // 'driver' => 'database', // 'table' => 'users', // ], ], /* |-------------------------------------------------------------------------- | 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', 'table' => 'password_resets', 'expire' => 60, 'throttle' => 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, ];