Changes
This commit is contained in:
f4ilji
@@ -0,0 +1,86 @@
|
||||
<?php
|
||||
|
||||
use Vormkracht10\TwoFactorAuth\Enums\TwoFactorType;
|
||||
use Vormkracht10\TwoFactorAuth\Http\Livewire\Auth\Login;
|
||||
use Vormkracht10\TwoFactorAuth\Http\Livewire\Auth\LoginTwoFactor;
|
||||
use Vormkracht10\TwoFactorAuth\Http\Livewire\Auth\PasswordConfirmation;
|
||||
use Vormkracht10\TwoFactorAuth\Http\Livewire\Auth\PasswordReset;
|
||||
use Vormkracht10\TwoFactorAuth\Http\Livewire\Auth\Register;
|
||||
use Vormkracht10\TwoFactorAuth\Http\Livewire\Auth\RequestPasswordReset;
|
||||
use Vormkracht10\TwoFactorAuth\Pages\TwoFactor;
|
||||
|
||||
return [
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Two Factor Authentication
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| This value determines which two factor authentication options are available.
|
||||
| Simply add or remove the options you want to use.
|
||||
|
|
||||
| Available options: email, phone, authenticator
|
||||
|
|
||||
*/
|
||||
'options' => [
|
||||
// TwoFactorType::authenticator,
|
||||
TwoFactorType::email,
|
||||
// TwoFactorType::phone,
|
||||
],
|
||||
|
||||
'enabled_features' => [
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Register
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| This value determines whether users may register in the application.
|
||||
|
|
||||
*/
|
||||
'register' => true,
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Tenant
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| Set to true if you're using Filament in a multi-tenant setup. If true, you
|
||||
| need to manually set the user menu item for the two factor authentication
|
||||
| page panel class. Take a look at the documentation for more information.
|
||||
|
|
||||
*/
|
||||
'multi_tenancy' => false,
|
||||
],
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| SMS Service
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| To use an SMS service, you need to install the corresponding package.
|
||||
| You then have to create a App\Notifications\SendOTP class that extends
|
||||
| the Vormkracht10\TwoFactorAuth\Notifications\SendOTP class. After that,
|
||||
| you can set the class alias in the sms_service key.
|
||||
|
|
||||
*/
|
||||
'sms_service' => null, // For example 'vonage', 'twilio', 'nexmo', etc.
|
||||
'send_otp_class' => null,
|
||||
'phone_number_field' => 'phone',
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Class Aliases
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| If you want to customize the pages, you can override the used classes here.
|
||||
| Make your that your classes extend the original classes.
|
||||
|
|
||||
*/
|
||||
'login' => Login::class,
|
||||
'register' => Register::class,
|
||||
'challenge' => LoginTwoFactor::class,
|
||||
'two_factor_settings' => TwoFactor::class,
|
||||
'password_reset' => PasswordReset::class,
|
||||
'password_confirmation' => PasswordConfirmation::class,
|
||||
'request_password_reset' => RequestPasswordReset::class,
|
||||
];
|
||||
@@ -0,0 +1,159 @@
|
||||
<?php
|
||||
|
||||
use Laravel\Fortify\Features;
|
||||
|
||||
return [
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Fortify Guard
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| Here you may specify which authentication guard Fortify will use while
|
||||
| authenticating users. This value should correspond with one of your
|
||||
| guards that is already present in your "auth" configuration file.
|
||||
|
|
||||
*/
|
||||
|
||||
'guard' => 'web',
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Fortify Password Broker
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| Here you may specify which password broker Fortify can use when a user
|
||||
| is resetting their password. This configured value should match one
|
||||
| of your password brokers setup in your "auth" configuration file.
|
||||
|
|
||||
*/
|
||||
|
||||
'passwords' => 'users',
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Username / Email
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| This value defines which model attribute should be considered as your
|
||||
| application's "username" field. Typically, this might be the email
|
||||
| address of the users but you are free to change this value here.
|
||||
|
|
||||
| Out of the box, Fortify expects forgot password and reset password
|
||||
| requests to have a field named 'email'. If the application uses
|
||||
| another name for the field you may define it below as needed.
|
||||
|
|
||||
*/
|
||||
|
||||
'username' => 'email',
|
||||
|
||||
'email' => 'email',
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Lowercase Usernames
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| This value defines whether usernames should be lowercased before saving
|
||||
| them in the database, as some database system string fields are case
|
||||
| sensitive. You may disable this for your application if necessary.
|
||||
|
|
||||
*/
|
||||
|
||||
'lowercase_usernames' => true,
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Home Path
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| Here you may configure the path where users will get redirected during
|
||||
| authentication or password reset when the operations are successful
|
||||
| and the user is authenticated. You are free to change this value.
|
||||
|
|
||||
*/
|
||||
|
||||
'home' => '/home',
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Fortify Routes Prefix / Subdomain
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| Here you may specify which prefix Fortify will assign to all the routes
|
||||
| that it registers with the application. If necessary, you may change
|
||||
| subdomain under which all of the Fortify routes will be available.
|
||||
|
|
||||
*/
|
||||
|
||||
'prefix' => '',
|
||||
|
||||
'domain' => null,
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Fortify Routes Middleware
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| Here you may specify which middleware Fortify will assign to the routes
|
||||
| that it registers with the application. If necessary, you may change
|
||||
| these middleware but typically this provided default is preferred.
|
||||
|
|
||||
*/
|
||||
|
||||
'middleware' => ['web'],
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Rate Limiting
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| By default, Fortify will throttle logins to five requests per minute for
|
||||
| every email and IP address combination. However, if you would like to
|
||||
| specify a custom rate limiter to call then you may specify it here.
|
||||
|
|
||||
*/
|
||||
|
||||
'limiters' => [
|
||||
'login' => 'login',
|
||||
'two-factor' => 'two-factor',
|
||||
],
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Register View Routes
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| Here you may specify if the routes returning views should be disabled as
|
||||
| you may not need them when building your own application. This may be
|
||||
| especially true if you're writing a custom single-page application.
|
||||
|
|
||||
*/
|
||||
|
||||
'views' => true,
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Features
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| Some of the Fortify features are optional. You may disable the features
|
||||
| by removing them from this array. You're free to only remove some of
|
||||
| these features or you can even remove all of these if you need to.
|
||||
|
|
||||
*/
|
||||
|
||||
'features' => [
|
||||
Features::registration(),
|
||||
Features::resetPasswords(),
|
||||
// Features::emailVerification(),
|
||||
Features::updateProfileInformation(),
|
||||
Features::updatePasswords(),
|
||||
Features::twoFactorAuthentication([
|
||||
'confirm' => true,
|
||||
'confirmPassword' => true,
|
||||
// 'window' => 0,
|
||||
]),
|
||||
],
|
||||
|
||||
];
|
||||
Reference in New Issue
Block a user