- What is eddusoft/filament-access-control-2fa used for?
- It is a Filament plugin for Laravel admin panels that combines role-based access control with two-factor authentication. The goal is to let you manage roles and permissions while protecting Filament logins with 2FA codes. The provided metadata does not document the full feature set, so review the repository README and source before adopting it.
- How do I install eddusoft/filament-access-control-2fa with Composer?
- Install it with Composer using the package name eddusoft/filament-access-control-2fa, then follow any publish and migration steps in the README. Because v1.0.1 was a package-name change, pin an exact version such as 1.0.1 rather than a floating constraint while the identity settles. Run php artisan package:discover after installation so Filament and Laravel auto-discovery pick up the service provider.
- Which Laravel versions does this Filament 2FA package support?
- The available metadata does not include a Laravel version support matrix. Check the require constraints in composer.json for the PHP version and illuminate/support range, and confirm the Filament major version it targets. Do not assume compatibility with your current Laravel LTS until those constraints match your application.
- What changed in v1.0.1 of eddusoft/filament-access-control-2fa?
- The v1.0.1 release is described as a rename-only change to publish the package under its final name. No functional logic changed, but the Composer identity may have changed along with the extra.laravel.providers auto-discovery entry. Treat it as an identity-breaking release if you already installed v1.0.0.
- Is the old package name still available on Packagist?
- The provided assessment does not state whether the old name was abandoned, aliased, or left resolvable. Verify on Packagist before relying on it, and document the old-to-new name mapping internally. An unregistered old name is a dependency-confusion risk if any team remains pinned to it.
- Do I need to change PHP namespaces after upgrading to v1.0.1?
- It is not clear from the available evidence whether the PSR-4 root namespace changed or only the Composer package name. Inspect composer.json autoload settings and the service provider namespace in the repository. If the namespace moved, update every use statement and any config or publish tags that embed the old name.
- Why is the package not discovered after I upgrade?
- The rename likely changed the extra.laravel.providers entry, so stale bootstrap cache can silently disable the package. Run composer clear-cache, php artisan config:clear, and php artisan package:discover, then re-run any vendor:publish commands against the renamed tags. Also check for duplicate installs where both the old and new package names are present.
- How does two-factor authentication work with Filament in this plugin?
- The package is described as securing Filament logins with 2FA codes while managing roles and permissions in the same admin panel. The exact enrollment flow, recovery codes, and supported authenticator apps are not detailed in the provided excerpt. Review the README and source code before promising specific 2FA behavior to users.
- Is eddusoft/filament-access-control-2fa production-ready?
- The only release signal provided is a rename patch at v1.0.1, with no substantive functional release history to evaluate. Intrinsic code risk appears low because no logic changed, but adoption and supply-chain risk are moderate for an immature release process. Pilot it in a low-traffic staging service and wait for a later patch without identity churn before production use.
- What alternatives exist for Filament access control and 2FA?
- Common comparisons include Filament Shield or Spatie Permission for role-based access control, and Laravel Fortify or Google2FA-based packages for two-factor authentication. This package's differentiator is combining both concerns in one Filament plugin. Evaluate maintenance activity, Laravel and Filament version support, and 2FA recovery options before choosing.