- How do I install kaantanis/filament-password-confirmation in a Laravel app?
- Install it with Composer, then register its RequirePassword middleware in the Filament panel or on the specific routes you want to protect. Because the package was last released in 2022, verify its Laravel and Filament constraints before installing and plan to test the redirect and auth flow in a non-production environment. Many teams should treat installation as a starting point for a fork rather than a permanent dependency.
- Which Laravel and Filament versions does this package support?
- The repository's last release is dated 2022-11-14, so it targets the Filament v2 and Laravel 9/10 era rather than modern Filament v3 or v4 and Laravel 11/12. Its Composer constraints and middleware assumptions are likely stale, so expect a port rather than a drop-in install. Check the composer.json and test against your exact PHP, Laravel, Filament, guard, and session driver versions.
- Does this package replace Laravel's native password.confirm middleware?
- No. Laravel's password.confirm middleware provides framework-level password confirmation for web routes, while this package adapts the idea into a Filament-specific RequirePassword middleware for panel routes. They can overlap, so choose one approach and avoid double-confirmation or conflicting redirects. For a maintained solution, a thin in-house middleware using Laravel's session confirmation semantics is usually cleaner.
- How does the RequirePassword middleware protect Filament panel routes?
- It checks whether the authenticated user has recently confirmed their password and redirects them to a confirmation screen when they have not. On success it records confirmation in the session and lets the original request continue. You must apply the middleware to the sensitive Filament panel routes or the panel middleware stack, and you should test redirects, guard behavior, and route coverage explicitly.
- Is filament-password-confirmation safe to use in production?
- It is medium-high risk as a production dependency because the project is archived, has few stars, and has had no security updates since 2022. The code is small enough to audit, vendor, or fork, but auth and session middleware must be correct and retested on every Laravel or Filament upgrade. Use it only with an assigned owner, tests, and a documented plan to replace it.
- How do I test password confirmation in a Filament panel with this package?
- Write feature tests that authenticate a user, request a protected Filament route, and assert a redirect to the confirmation screen. Then submit the correct and incorrect password and assert access or denial, including the return-to URL. Also test JSON or API-style requests, custom guards, and repeated requests after confirmation to catch redirect loops and session mismatches.
- Why is filament-password-confirmation archived and what does that mean for maintenance?
- The package was archived after its last release on 2022-11-14, so there is no upstream maintainer fixing compatibility or security issues. That means your team owns the fork, dependency pins, security review, and upgrade work if you adopt it. The operational burden is high relative to the package's small feature scope, which is why many teams reimplement it internally.
- What are alternatives to filament-password-confirmation for Filament panels?
- The most reliable alternative is a small in-house RequirePassword middleware built on Laravel's native password confirmation session behavior and wired into your Filament panel auth flow. You can also fork this package into your application namespace, pin it, add tests, and document ownership. There is no well-maintained, widely adopted Filament-specific package that guarantees support for modern Filament and Laravel versions.
- Does filament-password-confirmation work with Laravel 11, Laravel 12, or Filament v3 and v4?
- There is no official support for those newer versions. The package's 2022 release predates Filament v3 and v4 and the latest Laravel releases, so its dependency constraints and middleware behavior are likely incompatible without changes. Treat it as a reference implementation and port the logic into middleware tested against your current framework and panel versions.
- How should redirects and JSON or API requests be handled with Filament password confirmation?
- Browser requests should redirect to a password confirmation page and then return to the originally requested Filament route, while JSON or API-style requests should receive a clear 423 Locked or similar response instead of an HTML redirect. Verify whether this archived middleware distinguishes those cases, because incorrect handling can cause redirect loops or broken API clients. Add tests for both request types and for unauthenticated, already-confirmed, and expired-session scenarios.