- How do I install guanguans/dcat-login-captcha in a Laravel application?
- Install it with Composer using composer require guanguans/dcat-login-captcha in a Laravel app that already uses Dcat Admin. Laravel auto-discovery registers the service provider, then publish the package config and confirm the Dcat Admin login page renders the captcha challenge. If the challenge does not appear, check Dcat Admin version compatibility and whether your login flow uses custom overrides.
- Which Laravel and PHP versions does guanguans/dcat-login-captcha support?
- The package is intended for Laravel applications running Dcat Admin, and version 4.1.0 updates its gregwar/captcha constraint to 2.1. The provided release context does not include a full Laravel/PHP compatibility matrix, so check the package composer.json and Packagist metadata for the exact constraints. Confirm gregwar/captcha 2.1's PHP floor against your runtime before upgrading.
- Does guanguans/dcat-login-captcha work with Dcat Admin 2.x?
- Yes, it is designed for standard Dcat Admin 2.x installations and hooks into the Dcat Admin login form rendering. Heavily customized login flows or custom authentication overrides may not work without changes. Test against the exact Dcat Admin version used in your app rather than assuming the latest version is representative.
- How do I configure the Dcat Admin login captcha length, size, and font?
- Publish the package configuration and review the available keys for captcha length, dimensions, distortion, expiration, and font paths. Set font and writable temp or storage paths that exist in your environment, then re-test the login page. The published config file and README are the source of truth for supported options.
- What runtime requirements are needed to generate captcha images?
- Image captchas typically require the GD extension, available fonts, and a writable temp or storage path. If any of these are missing, the Dcat Admin login page can fail instead of degrading gracefully. Verify GD, font availability, and write permissions in CI, Docker images, and production servers.
- Is guanguans/dcat-login-captcha compatible with gregwar/captcha 2.1?
- Version 4.1.0 raises the package's constraint to gregwar/captcha 2.1, so it depends on that library version. Check whether other Composer packages in your app pin gregwar/captcha 1.x, because a transitive downgrade or conflict may be required. Confirm the PHP floor and API compatibility of gregwar/captcha 2.1 before deploying.
- Does this captcha replace rate limiting or MFA for Laravel admin login security?
- No. An image captcha is a weak control against modern automated attacks and should complement, not replace, rate limiting, account lockout, MFA, and login anomaly monitoring. Use it as one low-effort bot-mitigation layer on the Dcat Admin login page. Also consider accessibility, since a visual captcha can create compliance and usability issues without an accessible fallback.
- How should I test guanguans/dcat-login-captcha before production?
- Add the package in a feature branch and pin to 4.1.0, then publish config and set captcha dimensions, length, and font paths for the environment. Run the full Dcat Admin login flow in staging, including failed-login and session-expiry paths. Verify GD and fonts in CI and production images, and test with the exact Dcat Admin version in use.
- Is guanguans/dcat-login-captcha actively maintained and what support is available?
- The package is small and release activity appears dependabot-driven, with 4.1.0 primarily a dependency update plus CI action bumps. Maintenance burden is low but concentrated on a single maintainer, so treat it as a community dependency rather than one with a commercial SLA. Support is through GitHub issues, and internal teams should own configuration, Dcat Admin compatibility testing, and incident triage.
- How do I roll back if guanguans/dcat-login-captcha breaks the Dcat Admin login page?
- Remove the package and its published config to roll back, ideally behind a feature flag or config toggle during the staging rollout. No database migration is expected, but confirm whether captcha state is stored in session or cache before removing it. If you need an alternative, pair Dcat Admin login hardening with rate limiting, MFA, and other bot-mitigation controls.