Weave Code
User Bundle Laravel Package
monofony/user-bundle
Monofony UserBundle integrates user management into Monofony applications: customer and admin user entities, authentication, registration, password reset and profile handling. It builds on Sylius resources and Symfony security to give you a ready-to-extend user system out of the box.
[READ-ONLY] Symfony user bundle with multiple users and OAuth support.
Frequently asked questions about User Bundle
- Can I install monofony/user-bundle in a Laravel application?
- No. It is a Symfony bundle — a Monofony fork of SyliusUserBundle — built on Symfony DI, Doctrine ORM mappings, and Symfony Security user providers. Laravel's container, Eloquent, and Illuminate\Auth guards cannot consume those natively, and direct Composer installation would conflict with Laravel's bootstrap and require a Symfony kernel shim.
- What does Monofony UserBundle include out of the box?
- It ships a ready-to-use User entity with email, roles, and account status, plus registration and login flows wired into Symfony Security. Profile management forms and controllers, password reset, a configurable User model, and integration with Monofony/Sylius customer concepts round it out, with extension points through events and services.
- Is monofony/user-bundle compatible with Eloquent and Laravel auth guards?
- No. It uses Doctrine ORM mappings and Symfony Security user providers, while Laravel uses Eloquent and Illuminate\Auth guards. No adapter ships with it, so any integration would be custom glue with no upstream support.
- Which PHP and Symfony versions does monofony/user-bundle v1.10.0 support?
- v1.10.0 is a PHP version-constraint change only: it adds PHP 8 support and removes PHP 7.3. Symfony and Doctrine version pins were not bumped, so those remain the likely binding constraint, and a 2021-era PHP 8 declaration typically means 8.0 rather than 8.3 or 8.4. Verify the actual constraint ceiling instead of assuming parity with current runtimes.
- Is monofony/user-bundle maintained and safe for production authentication?
- No. The repository is marked read-only with 1 star and 0 dependents, and v1.10.0 is the first release since April 2021 — a single PHP-version PR. There is no published security policy, no CVE response path, and no PR merges, which is a critical gap for authentication code. Treat it as a reference design, not a production dependency.
- How does Monofony UserBundle handle registration, login, and password reset?
- Registration and login flows are wired into Symfony Security, with forms and controllers provided, and profile management plus password reset handling included. It builds on Sylius resources and Doctrine entities rather than Laravel's auth stack. In Laravel, Breeze, Jetstream, Fortify, and Sanctum cover the same ground.
- Can I add custom fields to the Monofony User entity?
- Yes. The User model is configurable and the bundle is extensible through events and services, so custom fields can be added with Doctrine mapping overrides and service or event hooks. That flexibility assumes a Symfony application with Doctrine, so it does not transfer to Laravel.
- Does Monofony UserBundle support OAuth and modern social login providers?
- OAuth support is part of its multi-user-type differentiator, but the OAuth code path was not touched in v1.10.0. A 2021-era implementation likely predates PKCE-first public clients, OIDC discovery expectations, and current Google, Microsoft, and GitHub provider APIs. Probe that surface before relying on it; in Laravel, Socialite is the standard answer.
- What are the Laravel alternatives for multiple user types and social login?
- Sanctum handles token and SPA auth with multiple guards and providers, Socialite covers social login, and Passport provides full OAuth2 server flows. Breeze, Jetstream, or Fortify scaffold registration, login, password reset, and profiles. Multiple user types are handled with separate models and guard providers, with no second runtime or dormant third-party auth bundle.
- How can I use monofony/user-bundle with Laravel if I need its multi-user features?
- Two paths exist and both are unattractive. A sidecar Symfony service exposing user and OAuth endpoints over HTTP adds a second runtime, a second deploy pipeline, and a network hop on every auth check. Porting the multi-model guard and OAuth logic into Laravel makes the package a reference design rather than a dependency, and direct Composer installation into Laravel is effectively not viable.
Weaver
How can I help you explore Laravel packages today?