Weave Code
Filament Auth Laravel Package
zvive/filament-auth
zvive/filament-auth integrates authentication into Filament panels for Laravel, providing login, registration, password reset, and email verification flows with configurable guards, middleware, and customizable views.
Filament Auth that has impersonation, profile pages, and permissions via spatie/laravel-permission OR silber/bouncer.
Frequently asked questions about Filament Auth
- What does zvive/filament-auth do for Laravel Filament panels?
- It integrates authentication flows such as login, registration, password reset, and email verification into Filament panels. It also provides impersonation, profile pages, and permissions through spatie/laravel-permission or silber/bouncer. It is best treated as an admin-console accelerator rather than a general-purpose auth replacement.
- How do I install zvive/filament-auth in a Laravel app?
- Install it with Composer as zvive/filament-auth, then publish and review its configuration and views according to the package README. Configure the desired guards, middleware, and Filament panel integration. Confirm the exact Filament and Laravel version constraints in composer.json before upgrading.
- Which Laravel, PHP, and Filament versions does zvive/filament-auth support?
- Compatibility claims include Laravel 8+ from a widget fix, but exact constraints are not fully clear from the provided context. You should verify PHP, Laravel, and Filament version requirements in the package composer.json and release notes. Treat Filament API coupling as a compatibility risk during upgrades.
- Can I use zvive/filament-auth with spatie/laravel-permission or silber/bouncer?
- Yes, the package supports permissions via spatie/laravel-permission or silber/bouncer. You need to choose and configure the authorization integration that fits your application. Review role and permission changes carefully, especially if Bouncer is enabled.
- How does impersonation work in zvive/filament-auth and is it safe for production?
- The package provides impersonation intended for support and admin workflows. Production safety depends on your audit, approval, and access controls, which are not detailed in the context. Restrict who can impersonate, log usage, and create runbooks before enabling it.
- Is zvive/filament-auth v2.3.2 a drop-in upgrade?
- No, v2.3.2 is a patch release that states a breaking change: visual display of dates will need to be updated. It also changes widget behavior, table actions, config-driven resources, and Filament table-action usage. Plan a controlled upgrade and regression-test all affected admin views.
- Does zvive/filament-auth work without Filament?
- No, the package targets Laravel applications that use Filament admin panels. If Filament is not your admin UI, integration cost rises sharply and the package is likely a poor fit. It is not positioned as a general Laravel auth replacement.
- How should I test zvive/filament-auth before deploying to production?
- Inventory existing auth and admin customizations, then upgrade in a sandbox with representative data. Update date-display templates and validate custom widgets, resources, and table actions. Wire create and update events to audit logging, run security and regression tests, and stage with support-team validation before rollout.
- Is zvive/filament-auth actively maintained and what alternatives exist?
- The release referenced is from 2022 and the changelog quality is inconsistent, so verify upstream activity and semver discipline. Alternatives include native Filament auth and user-management patterns, Laravel Breeze or Jetstream combined with Filament integrations, or custom user resources. If activity is low, consider pinning, forking, or vendoring the package.
- What production risks should I review with zvive/filament-auth?
- Key risks include date-display regressions across admin views, Filament API coupling, config and resource assumptions, removed widget pagination, and impersonation or Bouncer security configuration. Pin versions, monitor Filament compatibility, and validate user-list widget behavior at large user counts. Treat the date-display change as a required UI migration item.
Weaver
How can I help you explore Laravel packages today?