User Bundle Laravel Package

Product Decisions This Supports

• User Authentication & Management: Accelerates development of Symfony-based applications requiring robust user registration, login, password recovery, and profile management without reinventing the wheel.
• Legacy System Modernization: Ideal for migrating older FOSUserBundle-dependent applications to newer Symfony versions (5.4+) while maintaining backward compatibility.
• Cost Efficiency: Avoids licensing costs of commercial user management solutions (e.g., Auth0, Okta) for internal or low-risk projects.
• Kimai Ecosystem Integration: Enables seamless user management for Kimai 2 or similar time-tracking/HR tools, reducing coupling with external auth services.
• Compliance & Security: Provides built-in features like password hashing (via Symfony Security), CSRF protection, and role-based access control (RBAC) out of the box.
• Roadmap Flexibility: Allows teams to prioritize core features (e.g., API integrations, SSO) while leveraging this bundle for foundational auth logic.

When to Consider This Package

• Avoid if:
  • You need long-term support or guaranteed backward compatibility (this is explicitly not a maintained public package).
  • Your project requires enterprise-grade features (e.g., MFA, advanced audit logs, or SSO like OAuth2/OpenID Connect) beyond basic auth.
  • You’re using Symfony <5.4 or >6.x (compatibility not guaranteed).
  • You need custom email templates or complex workflows (mailer functionality is planned for removal).
  • Your team lacks PHP/Symfony expertise to debug or extend the forked codebase.
• Consider if:
  • You’re building a quick MVP or internal tool with standard user flows (registration, login, password reset).
  • You’re forking Kimai 2 or a similar project and need a compatible user bundle.
  • You prefer MIT-licensed, open-source solutions over proprietary auth services.
  • Your roadmap includes removing FOSUserBundle and modernizing dependencies.

How to Pitch It (Stakeholders)

For Executives:

"This package lets us ship user authentication—registration, login, and password recovery—in weeks instead of months, using battle-tested code from Kimai’s team. It’s free (MIT license), reduces vendor lock-in, and aligns with our Symfony stack. While not a long-term support solution, it’s a smart short-term play to avoid licensing costs and accelerate feature delivery for [Project X]. We’d pair it with our roadmap to eventually replace it with a more scalable auth service (e.g., Auth0) once we hit [growth milestone]."

For Engineering:

*"This is a lightweight, forked FOSUserBundle optimized for Symfony 5.4+ and Kimai 2. It strips out deprecated code and adds tagged releases—perfect for:

• Quick auth scaffolding (no need to configure FOSUserBundle manually).
• Kimai 2 compatibility (avoids dependency conflicts).
• Customization (extend the user entity or add fields via Doctrine). Tradeoffs: No active maintenance, so we’d need to monitor for breaking changes. Ideal for prototypes or internal tools where auth isn’t the core differentiator. For production-critical apps, we’d recommend [alternative package] or a dedicated auth service."*

For Developers:

*"Pros:

• Zero setup: Just drop it into your Symfony project and enable the bundle.
• Modernized: No deprecation warnings (unlike FOSUserBundle).
• Flexible: Override templates/controllers easily via Symfony’s bundle inheritance. *Cons:
• Not for public use: The repo warns against manual installation—treat it like a private dependency.
• Limited features: No built-in email customization (mailer is being removed). Use case: Great for side projects, admin panels, or when you need auth fast but can handle occasional updates. For anything else, use [SymfonyCast’s MercureUserBundle] or a dedicated auth service."*