- How do I install asundust/auth-captcha in a Laravel application?
- Install it through Composer with composer require asundust/auth-captcha, then publish the package configuration so you can tune captcha and throttling behavior. The package registers a service provider and middleware at the framework layer, so registration follows the standard Laravel pattern. Because version 3.0.0 requires PHP 8.0 or newer and Laravel 9.x as a floor, confirm your framework version before running composer update.
- Does asundust/auth-captcha support Laravel 10 and Laravel 11, or only Laravel 9?
- The 3.0.0 release drops older targets and sets Laravel 9 as the minimum, but the release notes are terse and do not clearly state whether the constraint is ^9.0 only or 9 and later. Check the package's composer.json on the repository before committing, since a ^9.0-only constraint creates a ceiling that will block your next framework upgrade. If the constraint excludes 10 and 11, plan for a fork or wait for a wider release.
- How do I add a sliding captcha to the laravel-admin login page?
- The package is built specifically for laravel-admin authentication, so it hooks into the admin login flow rather than requiring custom view work in most cases. Install it, publish the config, and ensure the middleware and service provider are registered for the admin route group. After that, the sliding captcha is generated and validated as part of the login submission.
- What changed between version 2.x and 3.0.0 of auth-captcha?
- Version 3.0.0 is a deliberate breaking release that removes support for Laravel 8 and earlier and aligns with Laravel's own release cadence. It also introduces new rate-limit parameters, which appear to be additive configuration rather than a structural rewrite. Applications still on older Laravel versions cannot consume 3.x fixes and must either upgrade the framework first or pin to the last 2.x release.
- How do I validate a sliding captcha in a custom Laravel controller or form request?
- The package exposes validation rules and middleware that integrate with Laravel's standard validation pipeline, so you can attach the captcha rule to a form request or inline validator. Generation and token verification happen inside the package, which means you consume the rule rather than writing image-comparison logic yourself. Confirm the exact rule name and payload field against the published config after installation.
- Can I use asundust/auth-captcha outside laravel-admin, such as with Laravel Breeze or Fortify?
- The package is positioned as a laravel-admin authentication plugin, so laravel-admin integration is the well-trodden path and the primary supported use case. The underlying captcha generation and validation rules are Laravel-native, which means wiring them into Breeze, Fortify, or a custom login controller is plausible but requires your own glue code. Prototype it in a scratch branch and verify generation, validation, and throttling behavior before relying on it.
- Do the new rate-limit parameters in 3.0.0 change default throttling?
- The rate-limit parameters appear additive, but the release notes are brief and localized, so the precise semantics and whether defaults shifted are unverified. A silent change in throttling defaults can surface as unexpected 429 responses in production where none appeared before. Characterize behavior under load against your 2.x baseline before rolling the upgrade out broadly.
- How do I publish and customize the auth-captcha configuration file?
- Publish the package config with the standard artisan vendor:publish command, then diff the published file against your existing copy to surface new keys such as the 3.0.0 rate-limit parameters. Keep the published config in version control so changes are reviewable rather than applied ad hoc on servers. The config file plus the Composer constraint is essentially the whole ongoing maintenance footprint.
- How do I test captcha-protected routes in Laravel without solving the image?
- Treat the captcha as a boundary and stub it in tests rather than attempting to solve the image programmatically. You can bind a fake validator, disable the middleware in the test environment, or bypass the rule in your test case setup so the rest of the auth flow is exercised. Keep one integration test that hits the real generation endpoint so regressions in the package are still caught.
- Is asundust/auth-captcha actively maintained, and what are the alternatives?
- Maintainer count, release cadence, issue backlog, and download volume are the health signals to check on the repository before adopting, since the release notes alone do not establish a support commitment. There is no documented 2.x LTS or security-support window in the material available, so teams pinning to 2.x should record the divergence in their dependency register. Alternatives include general Laravel captcha packages and framework-native throttling, but few target laravel-admin login specifically.