[ 'guard' => env('AUTHENTICATION_GUARD', 'web-guard'), 'passwords' => 'users', ], /* |-------------------------------------------------------------------------- | Authentication Proxy Headers |-------------------------------------------------------------------------- | | When using a reverse proxy for authentication this option controls the | default name of the headers sent by the proxy. | */ 'auth_proxy_headers' => [ 'user' => env('AUTH_PROXY_HEADER_FOR_USER', 'REMOTE_USER'), 'email' => env('AUTH_PROXY_HEADER_FOR_EMAIL', null), ], /* |-------------------------------------------------------------------------- | 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-guard' => [ 'driver' => 'session', 'provider' => 'users', ], 'api-guard' => [ 'driver' => 'passport', 'provider' => 'users', 'hash' => false, ], 'reverse-proxy-guard' => [ 'driver' => 'reverse-proxy', 'provider' => 'remote-user', ], ], /* |-------------------------------------------------------------------------- | 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-2fauth', 'model' => App\Models\User::class, ], 'remote-user' => [ 'driver' => 'remote-user', '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', 'table' => 'password_resets', 'expire' => 60, 'throttle' => 60, ], // for WebAuthn 'webauthn' => [ 'provider' => 'users', // The user provider using WebAuthn. 'table' => 'web_authn_recoveries', // The table to store the recoveries. '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, ];