- How do I install artmin96/filament-password-less in a Laravel app?
- Install it with Composer, then publish any provided configuration and migration files before registering the package with your Filament panel. The package is intended for Laravel and Filament applications, and release 1.0.3 adds Laravel 10.x support. Confirm your PHP, Laravel, Filament, database, mail, and session driver versions in a non-production environment first.
- Does filament-password-less support Laravel 10 and Filament?
- Yes, release 1.0.3 explicitly adds Laravel 10.x support through a compatibility pull request. The available context does not confirm Laravel 11 or older Laravel versions, and it does not list specific Filament major versions. Validate the exact Laravel 10 minor version, Filament version, and PHP version you plan to use.
- Can I keep password login enabled while testing passwordless authentication?
- You should keep password login enabled during evaluation because the package is a single-purpose passwordless auth extension, not a full identity platform replacement. The recommended migration path is to run a staging proof of concept and introduce magic-link login as an optional or parallel path before any enforced cutover. Keep a rollback path to password authentication until operational confidence is established.
- How does the magic-link token lifecycle work and what security checks are needed?
- The package adds email magic-link login, but the exact token storage, expiry, reuse, and replay-protection model should be verified in the source and configuration. Authentication is security-sensitive, so review token entropy, single-use behavior, expiry, rate limiting, user enumeration protection, session fixation handling, and account recovery. Add host-application controls where the package does not provide them.
- Is filament-password-less production ready for Filament admin panels?
- It is best treated as a narrow passwordless authentication extension for Laravel and Filament rather than a proven general identity platform. Release 1.0.3 is a Laravel 10 compatibility milestone, not proof of production maturity. Use staging, pin the package version, review the authentication code, and test mail delivery, lockout behavior, and rollback before rolling it out to admins.
- How do I test passwordless login and email delivery for Filament?
- Start in local or staging with a small admin user cohort, configure the same mail and queue settings you expect in production, and verify magic-link generation, delivery, expiry, and reuse behavior. Test what happens when the mail provider is unavailable and confirm that login failures are handled safely. Keep password login available during testing so administrators are not locked out.
- Can I customize the magic-link email or use SMS instead?
- The package is described as configurable, but the provided context does not confirm which notification channels or templates are supported. Check the package configuration and notification classes to see whether the email message can be customized and whether SMS or other channels are available. Validate delivery, branding, and failure handling before production use.
- Are rate limiting, audit logging, and user-enumeration protections built in?
- The available technical assessment flags rate limiting, audit logging, user enumeration, token replay, and session fixation as risks that must be validated. It does not confirm that these protections are built into the package, so they may need to be added in the host Laravel application. Review middleware, login attempt tracking, logging, and generic response messages before rollout.
- What alternatives should I consider for passwordless Filament authentication?
- You can evaluate Laravel-native signed URLs and notification patterns, dedicated authentication packages, or a custom magic-link flow built around Laravel guards and notifications. The right choice depends on whether you need admin-only passwordless access or a broader customer identity platform. Compare security controls, Filament integration, maintenance activity, and fallback behavior before adopting any option.
- Who maintains filament-password-less and how actively is it updated?
- The package has a small maintainer footprint and community-only support, so maintenance ownership effectively sits with your application team. Release 1.0.3 shows recent Laravel 10 compatibility work, but you should pin versions and review future releases rather than assuming ongoing support. Plan for internal code review, upgrade testing, and a maintained fork if the package becomes critical.