- What Laravel versions does hesto/multi-auth support?
- Hesto MultiAuth targets Laravel 5.3 through 5.7. Treat those versions, along with PHP 7.x, as hard compatibility boundaries until you verify otherwise in a clean branch. It is not designed for Laravel 6 or later, and dependency constraints are likely to block modern framework and PHP versions.
- How do I install hesto/multi-auth?
- Install it with Composer inside a Laravel 5.3–5.7 application that meets the package's PHP 7.x constraints. Installation is only the first step: you still need to configure guards, providers, models, password brokers, middleware, and login or registration flows. Run a short spike in an isolated branch to prove one end-to-end login and logout flow before adopting it.
- Can I use hesto/multi-auth with Laravel 8, 9, or 10?
- No, not reliably. The package is scoped to Laravel 5.3–5.7, and its Composer constraints will likely block Laravel 6 and newer. Modern Laravel already supports multiple guards and providers natively, so use native auth configuration or a current starter kit instead.
- How do I configure multiple guards and models with hesto/multi-auth?
- You configure separate guards, providers, models, tables, and password brokers for each account type, such as users and admins. This is not a drop-in toggle; it requires coordinated changes across auth configuration, middleware, routes, and login or registration flows. Map every guard and model you need before changing code, then test guard isolation explicitly.
- Does hesto/multi-auth support separate login, registration, and password reset for admins?
- Yes, the package is intended to provide login, registration, password reset, middleware, and Blade helpers for each configured account type. That lets you keep separate models and tables for users, admins, or other account types. Verify each flow, including remember-me and password reset, with automated tests because the package is aged.
- Is hesto/multi-auth still maintained and safe for production?
- Treat it as high risk. The package appears aged, supports only end-of-life Laravel versions, and has a weak long-term support signal. There are real concerns about unpatched security issues, sparse documentation, and reliance on framework internals that changed after Laravel 5.7. If you must use it, pin versions, review security, and plan an exit.
- What are alternatives to hesto/multi-auth in modern Laravel?
- Use Laravel's native multiple guards and providers with Auth::guard(), plus custom user providers when you need separate tables. For session-based auth, Laravel Breeze, Jetstream, or Fortify are common choices; for API auth, consider Sanctum. Often role scoping or a single users table with roles is simpler than maintaining multiple user models.
- How does hesto/multi-auth handle middleware and Blade helpers for multiple guards?
- The package provides middleware and Blade helpers intended to work per guard, so you can protect routes and render auth-aware UI for each account type. You still need to register middleware aliases, organize route groups, and confirm session behavior for each guard. Test guard isolation carefully so an admin session cannot satisfy a user-only route or vice versa.
- What PHP versions and dependency constraints does hesto/multi-auth require?
- It is built for PHP 7.x and Laravel 5.3–5.7, so those are the practical boundaries. Validate Composer constraints in a clean branch and inspect transitive dependencies before installing into an existing application. Modern PHP 8+ and current Laravel releases are likely incompatible.
- How do I migrate away from hesto/multi-auth to native Laravel auth?
- Inventory every guard, provider, model, middleware alias, route group, password broker, and session setting that the package touches. Replace package behavior with native auth.php guard and provider definitions, adding custom user providers where separate tables are required. Cut over guard by guard behind feature flags, keep rollback paths, and isolate package usage behind application-level auth services until removal is complete.