Weave Code
Breeze Multiauth Laravel Package
painlesscode/breeze-multiauth
Adds multi-authentication support to Laravel Breeze, helping you scaffold separate guards, login flows, and redirects for multiple user types such as admins and regular users with Breeze-style routes, views, and middleware.
Multi authentication guard generator for laravel breeze.
Frequently asked questions about Breeze Multiauth
- How do I install painlesscode/breeze-multiauth?
- Install it with Composer into a fresh Laravel application that already has an unmodified Laravel Breeze installation, then run the package's generator command as described in its README. It is a scaffolding-time tool, so it should be required in development and run before you customize Breeze views, routes, or auth config. Verify the exact command and supported Breeze version in the repository before running it.
- Does painlesscode/breeze-multiauth support Laravel 10 and Laravel 11?
- No, it was released in February 2022 against the Laravel 8/9 and PHP 8.0/8.1 era, and there have been no releases since. Breeze changed its view stack, Inertia/React/Vue presets, and PHP minimums in Laravel 10 and 11, so stubs generated for an older Breeze may reference removed components or outdated middleware registration. Treat Laravel 10/11 support as unproven unless you validate it yourself in a throwaway app.
- Is breeze-multiauth a replacement for role-based authentication?
- No. It scaffolds genuinely separate user populations, each with its own Eloquent model, provider, password broker, session guard, routes, and middleware. If you only need roles or permissions within a single users table, this package over-engineers the auth layer and a role/permission package is a better fit. Use it when admins, customers, or vendors are distinct actors with separate credential stores.
- Can I add multi-auth to an existing Laravel app with breeze-multiauth?
- It is intended for a greenfield or nearly greenfield app with an unmodified Breeze install, and there is effectively no migration path into an existing customized application. The generator patches or publishes files, so retrofitting into a diverged Breeze tree risks merge conflicts and silently mis-wired guards. The realistic approach is to scaffold in a throwaway reference app, inspect the generated code, and hand-port what you need.
- Does breeze-multiauth generate password reset and email verification for each guard?
- The package's focus is separate guards, login flows, routes, views, and redirects, but per-guard password reset brokers, email verification, and remember-me behavior should be verified rather than assumed. The evaluation notes this as an open question, so inspect the generated auth config, password broker entries, middleware, and controllers in a test app. If those flows are incomplete, you will need to wire them manually for each guard.
- What license is painlesscode/breeze-multiauth released under?
- The repository reports NOASSERTION, meaning it does not declare a recognized license. Under default copyright that leaves no explicit grant to use, modify, or redistribute the code, which is a legal blocker for commercial products until clarified with the author. Treat it as an evaluation-only artifact and ask the maintainer to add an explicit OSI license.
- Is painlesscode/breeze-multiauth still maintained?
- It appears to be a single-maintainer, low-traffic project: the last release was 2022-02-19 and the repository has around 47 stars. There is no evidence of ongoing compatibility work for newer Laravel or Breeze versions. Plan for the generated code to be a one-shot handoff that your team owns and upgrades forever.
- Does breeze-multiauth work with Sanctum, Passport, Jetstream, or Fortify?
- It is built around Laravel Breeze's session-based auth and is a poor fit for API-first or SPA token architectures using Sanctum or Passport. It is also orthogonal to Jetstream and Fortify, which already ship their own auth primitives, and mixing them is not worth the debugging cost. Use it only when Breeze session guards match your architecture.
- Can I customize the generated guards or add more user types?
- Yes, once generated the guards, models, providers, middleware, routes, and controllers become ordinary code in your repository, so you can edit them freely. You can add further guards by following the same config and provider patterns the package scaffolds. Keep in mind that regenerating or re-running the tool over customized files may overwrite or conflict with your changes, so commit before running it.
- How should I test multi-guard authentication after using breeze-multiauth?
- Stand up a throwaway reference app, install the matching Breeze version, run the generator, and commit the result so you can inspect exactly what changed. Then write feature tests for each guard's login, logout, redirect, middleware protection, password reset, and remember-me behavior, and verify that users cannot cross between guards. Also check route names, session keys, and password broker configuration for collisions.
Weaver
How can I help you explore Laravel packages today?