Rich authentication logic and scaffoldings for your Laravel applications.
In today's digital landscape, the authentication process for most web applications has evolved beyond basic username-password logins. Modern authentication systems must consider password strength, two-factor authentication, secure account recovery, and even passwordless login methods like Passkeys. Implementing a robust, secure, and maintainable authentication solution can be a challenging task, requiring significant effort and expertise.
This monorepo contains an authentication library, along with a collection of adapter packages that leverage the library, to deliver a comprehensive authentication framework for your applications.
- Basic email-password or username-password based authentication.
- Passkey-based ("passwordless") authentication.
- Two factor authentication for password-based users (TOTP, Security Keys).
- Email verification, either directly after registration or manually.
- Sudo-mode, allowing the user to temporarily elevate their privileges and perform sensitive actions.
- Account recovery (requires the generation of recovery codes).
- A rich set of authentication events, such as
MultiFactorChallenged
,AccountRecoveryFailed
, etc.
To use this authentication library, you'll likely want to install an adapter package, which use the 'core' package internally. Here are some of the available adapter packages:
Package | Description | Composer Require |
---|---|---|
Laravel Auth Bladebones | An extremely basic, unthemed Blade adapter | composer require claudiodekker/laravel-auth-bladebones |
composer require claudiodekker/laravel-auth-blade |
||
composer require claudiodekker/laravel-auth-inertia |
If you're looking to develop your own adapter, we recommend using the Bladebones adapter repository as a starting point, as it already contains all the necessary scaffolding in it's most barebones form (hence the name).
composer test
Please see CHANGELOG for more information what has changed recently.
Please see CONTRIBUTING for details.
If you discover any security related issues, please email [email protected] instead of using the issue tracker.
This way, we can safely discuss and resolve the issue (within a reasonable timeframe), without exposing users to the unnecessary additional risk. Once the issue is fixed and a new version is released, we'll make sure to credit you for your contribution (unless you wish to remain anonymous).
The MIT License (MIT). Please see License File for more information.