Laracastle is a package that automates the installation and configuration of castle.io for your Laravel site.
Castle.io proactively protects your users from account hacking. When you subscribe to their service, they make intelligent decisions when users attempt to login to your site or access protected resources.
For more information, I recommend checking out their site.
Castle.io is not difficult to integrate, but it does take some work.
With this package, you can integrate castle.io's services within minutes instead of hours or even days.
Via Composer
$ composer require robrogers3/laracastleLaracastle pretty much depends on the Laravel Auth package. On Laravel 6, Auth is a separate package. So first install it. Without the Auth package you will have A LOT of work to do.
composer require laravel/ui --dev
Then do one of these:
php artisan ui bootstrap --auth
# or
php artisan ui vue --auth
# or
php artisan ui react --auth
And, then of course run this:
php artisan migrate
Also if you plan to use Email Verification to protect important routes, which is recommended, you will need to configure the mail driver.
After you have required the package via composer, run:
php artisan vendor:publish --provider='robrogers3\laracastle\LaracastleServiceProvider'
Next, set up castle.io.
If you don't know your castle.io APP_ID or SECRET, then you need to sign up for castle.io.
Then, update update your .env files, like so:
CASTLE_SECRET=YOUR_CASTLE_SECRET
CASTLE_APP_ID=YOUR_CASTLE_APP_ID
CASTLE_MODE=[evaluation|production]
HOME_ROUTE='/home'
When you are just starting out, set the CASTLE_MODE to 'evaluation'. Once you are ready to take action, change the CASTLE_MODE to 'production.'
Also, castle requires a HOME_ROUTE, which defaults to 'home', you can change this if your 'home' route changes.
To have Castle.io integrated in minutes just run this command:
NOTE: this will CLOBBER your User class and your AppServiceProvider.
php artisan laracastle:install
Add this line to your main layouts blade file (e.g. app.blade.php) in the head section:
@include('vendor/robrogers3/headscript/laracastle')
Use "Email Verification" to protected your routes to greatly reduce your headaches!
By default, if castle.io challenges a login attempt then Laracastle will ask your user to login again, which can be a pain. A better alternative is to ensure users have verified their email address via the MustVerifyEmail interface.
To start, first learn about Laravel's Email Verification.
Next update your Auth routes in routes/web.php like so:
Auth::routes(['verify' => true]);
Then make sure your user implements 'MustVerifyEmail' and 'Laracastle\UserInterface'.
You will also need to add these two traits to your user model:
- ResetsAccounts, and
- ChecksVerification
Your User class will look like this:
use robrogers3\Laracastle\UserInterface;
use robrogers3\Laracastle\Traits\ChecksVerification;
use robrogers3\Laracastle\Traits\ResetsAccount;
use Illuminate\Contracts\Auth\MustVerifyEmail;
use Illuminate\Foundation\Auth\User as Authenticatable;
use Illuminate\Notifications\Notifiable;
class User extends Authenticatable implements MustVerifyEmail, UserInterface
{
use Notifiable, ResetsAccount, ChecksVerification;
//...
}
Lastly, protected routes that should be verified by email. Like so:
Route::get('home', function () {
// Only verified users may enter...
})->middleware('verified'); // verified middleware is the key!
Optional but Recommended: Add this to your AppServiceProvider
//...
use App\User;
use robrogers3\Laracastle\UserInterface;
//...
public function boot()
{
$this->app->bind(UserInterface::class, function ($app) {
return User::class;
});
}
First head over to Web Hooks on your Castle.io Dashboard.
And set two webhook end points:
- For the '$incident.confirmed' event add this endpoint:
https://your-base-url.com/laracastle/compromised-webhook
- For the '$review.opened' event add this endpoint:
https://your-base-url.com/laracastle/review-webhook
Do NOT select Subscribe to All Events for either endpoint.
Note the second webhook is recommended but optional.
Next, if you're feeling ambitious, style the review device page.
You can find it in:
./resources/views/vendor/robrogers3/pages/device.blade.php
Congrats you’re done. Your users are now protected by castle.io.
Laracastle hooks into several events dispatched by Laravel related to the user authentication processes. Like: Logging In, Logging Out, and Resetting Passwords. Most important is the Login Event.
When the Login Event is fired, Laracastle makes a realtime request to castle.io to determine if the request looks 'suspicious' or 'authentic'. And depending on the level of suspiciousness, it can either Allow the login, Challenge the login, or Deny the Login.
If the Login is allowed, then Laracastle proceeds as per usual.
If the Login is challenged, then we either ask the user to verify their email address, or request that they login again. (See config )
If the Login is denied, then we disallow Login, and then Laravel will take over to lock the account for a specified duration. Learn more about throttling requests on Laravel.com.
If Castle.io determines that an account may have been compromised, it sends a request to a webhook in Laracastle. Laracastle uses this information to reset the user's account password, and then notify them via email that their account may have been compromised and that they need to reset their password before they can access protected resources.
When castle.io believes there has been unusual or suspicious device activity accessing your account, it sends another webhook to Laracastle. Laracastle uses this information to notify the user of the activity, and asks them review it.
On clicking 'Review Device' from the notification, they are able to see the details of the activity. The user can either confirm it was valid activity, or report it as invalid. If it is valid, the suspicious activity is resolved, otherwise, the activity is escalated. When escalated the compromised webhook will be run, the account password will be reset, and the user will be notified via email.
Please see the changelog for more information on what has changed recently.
$ composer testPlease see contributing.md for details and a todolist.
If you discover any security related issues, please email author email instead of using the issue tracker.