- Can I use ezsystems/ezplatform-user in a Laravel project?
- No, this package is **exclusively for eZ Platform 6.x/7.x** and has no native Laravel compatibility. It relies on eZ’s kernel, Doctrine DBAL, and Symfony Security, which conflict with Laravel’s Eloquent and DI container. For Laravel, use Laravel Fortify or Breeze instead.
- What Laravel versions does this package support?
- This package **does not support Laravel**—it’s built for eZ Platform, which is a separate PHP framework. If you’re migrating from eZ to Laravel, you’ll need to rebuild user management using Laravel’s auth system (e.g., Fortify) or create an API bridge.
- How do I migrate user data from eZ Platform to Laravel?
- There’s no built-in migration tool. You’ll need to export user data from eZ (e.g., via REST API or database dumps) and manually import it into Laravel using Eloquent or custom scripts. Consider using Laravel’s `HasApiTokens` for API-based syncs if needed.
- Does this package support OAuth/SSO in Laravel?
- No, this package is tied to eZ Platform’s authentication system, which doesn’t integrate with Laravel’s OAuth providers (e.g., Sanctum, Passport). For Laravel, use packages like Laravel Socialite or Passport for SSO.
- What’s the best way to integrate eZ Platform users with Laravel?
- The lowest-risk approach is to expose eZ’s user data via a **REST/gRPC API** and consume it in Laravel. Avoid direct integration due to dependency conflicts. For gradual migration, use the strangler pattern: replace eZ auth with Laravel’s while keeping eZ as a legacy service.
- Can I use this package alongside Laravel’s Eloquent?
- No, this package uses Doctrine DBAL and eZ’s ORM, which are incompatible with Eloquent. If you need to share user data, create a **database view** or sync via API. Direct ORM integration will cause conflicts.
- What are the alternatives to ezplatform-user for Laravel?
- For Laravel, use **Laravel Fortify** (auth scaffolding), **Breeze** (Blade-based auth), or **Jetstream** (Livewire/Inertia). For roles/permissions, **Spatie Laravel-Permission** is a drop-in replacement. Avoid this package unless you’re tightly coupled to eZ Platform.
- Does the new generator workflow (IBX-5569) help with Laravel integration?
- No, the generator workflow is an **internal eZ Platform optimization** for content/user templates and has no impact on Laravel. It’s irrelevant to Laravel’s auth system or user management. Focus on API-based integration instead.
- How do I handle roles and permissions in Laravel if I’m using this package?
- This package’s role system won’t work with Laravel. Map eZ’s `ezuser_group` to Laravel using **Spatie Laravel-Permission** or a custom solution. Sync roles via API or manual database updates, but expect manual effort due to architectural differences.
- Is this package actively maintained for Laravel?
- No, this package is **not Laravel-compatible** and has no plans for Laravel support. Ibexa (formerly eZ Systems) focuses on eZ Platform, not Laravel integration. If you need Laravel features, rebuild user management using native Laravel packages.