koel/config/auth.php

99 lines
3.4 KiB
PHP
Raw Normal View History

2015-12-13 04:42:28 +00:00
<?php
return [
/*
|--------------------------------------------------------------------------
2015-12-27 09:12:10 +00:00
| Authentication Defaults
2015-12-13 04:42:28 +00:00
|--------------------------------------------------------------------------
|
2015-12-27 09:12:10 +00:00
| 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.
2015-12-13 04:42:28 +00:00
|
*/
2015-12-27 09:12:10 +00:00
'defaults' => [
'guard' => 'web',
'passwords' => 'users',
],
2015-12-13 04:42:28 +00:00
/*
|--------------------------------------------------------------------------
2015-12-27 09:12:10 +00:00
| Authentication Guards
2015-12-13 04:42:28 +00:00
|--------------------------------------------------------------------------
|
2015-12-27 09:12:10 +00:00
| 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"
2015-12-13 04:42:28 +00:00
|
*/
2015-12-27 09:12:10 +00:00
'guards' => [
'web' => [
'driver' => 'session',
'provider' => 'users',
],
'api' => [
'driver' => 'token',
'provider' => 'users',
],
],
2015-12-13 04:42:28 +00:00
/*
|--------------------------------------------------------------------------
2015-12-27 09:12:10 +00:00
| User Providers
2015-12-13 04:42:28 +00:00
|--------------------------------------------------------------------------
|
2015-12-27 09:12:10 +00:00
| 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"
2015-12-13 04:42:28 +00:00
|
*/
2015-12-27 09:12:10 +00:00
'providers' => [
'users' => [
'driver' => 'eloquent',
'model' => App\Models\User::class,
],
// 'users' => [
// 'driver' => 'database',
// 'table' => 'users',
// ],
],
2015-12-13 04:42:28 +00:00
/*
|--------------------------------------------------------------------------
2015-12-27 09:12:10 +00:00
| Resetting Passwords
2015-12-13 04:42:28 +00:00
|--------------------------------------------------------------------------
|
| Here you may set the options for resetting passwords including the view
2015-12-27 09:12:10 +00:00
| that is your password reset e-mail. You may also set the name of the
2015-12-13 04:42:28 +00:00
| table that maintains all of the reset tokens for your application.
|
2015-12-27 09:12:10 +00:00
| 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.
|
2015-12-13 04:42:28 +00:00
| 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.
|
*/
2015-12-27 09:12:10 +00:00
'passwords' => [
'users' => [
'provider' => 'users',
'email' => 'auth.emails.password',
'table' => 'password_resets',
'expire' => 60,
],
2015-12-13 04:42:28 +00:00
],
];