Version 3.4.1 of laravel-two-factor-authentication

Fixed

• Don't allow float tokens #14

Version 3.4.0 of laravel-two-factor-authentication

Added

• Laravel 11 compatibility

Version 3.3.0 of laravel-two-factor-authentication

Added

• Laravel 10 compatibility

Version 3.2.0 of laravel-two-factor-authentication

Added

• Laravel 9 compatibility

Version 3.1.0 of laravel-two-factor-authentication

Added

• The possibility to customise the route to which a user will be redirected in case of submitting an invalid token. See the documentation for more information.

Version 2.8.1 of laravel-two-factor-authentication

Added

• The possibility to customise the route to which a user will be redirected in case of submitting an invalid token. See the documentation for more information.

Version 3.0.0 of laravel-two-factor-authentication

Added

• Proper support for Laravel 8. Note: This is a breaking change. Version 3 of this package is not backwards compatible with Laravel versions prior to 8 due to a breaking change in \Illuminate\Support\Manager. If you want to use this package with Laravel 5, 6 or 7 you will need to use version 1 or 2 of this package.
• Factory class MichaelDzjap\TwoFactorAuth\Database\Factories\TwoFactorAuthFactory for model MichaelDzjap\TwoFactorAuth\Models\TwoFactorAuth

Changed

• In Laravel 8 model namespacing has changed. Hence, MichaelDzjap\TwoFactorAuth\TwoFactorAuth should now be imported as MichaelDzjap\TwoFactorAuth\Models\TwoFactorAuth instead

Version 2.7.0 of laravel-two-factor-authentication

Removed

• Due to breaking changes in \Illuminate\Support\Manager the 2.x version of laravel-two-factor-authentication doesn't work with Laravel 8. Hence, the support of Laravel 8 has been revoked. Version 3.x and up of laravel-two-factor-authentication will re-add support for Laravel 8.

Version 2.6.2 of laravel-two-factor-authentication

Added

• Laravel 8 support.

Version 2.6.1 of laravel-two-factor-authentication

Fixed

Use the user model defined in the config file in the package. Until now this wasn't actually enforced and using a custom user model in the config (i.e. anything else than \App\User) would result in type errors and incorrect db querying behaviour. Unfortunately this means we lose type hinting for function arguments for users...