Getting Started

Install with composer require happenv-com/filament-passkeys, then publish/run any package migrations and publish the package config if exposed.
Register the package’s Filament plugin in the relevant panel provider and confirm the panel’s auth guard is the one you want passkeys associated with.
Look first at the package README, config/filament-passkeys.php if present, the published migration/credential table, and the Filament panel provider where the plugin is registered.
First practical use case: log in normally as an existing Filament user, enroll a passkey from the user/profile area, log out, then verify passkey login works on HTTPS or localhost.

Implementation Patterns

Add passkey enrollment as a profile/security action rather than forcing it during registration; this keeps the first login flow simple and lets existing users opt in.
Use passkeys as an additional Filament login method with password login still available as fallback, especially during rollout.
For multi-panel apps, register/configure the plugin per panel and verify credentials are scoped to the intended guard/user model.
Treat each WebAuthn ceremony as a fresh challenge: request a challenge immediately before registration/authentication, and do not cache or reuse challenge state across attempts.
In v1.4.2, the prompt now starts per challenge rather than per page load. If your UI previously depended on one prompt per page load, re-test repeated passkey attempts and multi-step auth flows.
For testing, exercise the browser flow manually on a secure origin; feature tests can cover endpoint/auth wiring, but full WebAuthn behavior usually needs browser-level or mocked JS coverage.

WebAuthn requires a secure context. Use HTTPS in staging/production and localhost for local development; reverse proxies must forward the correct scheme/host.
RP ID/origin configuration must match the browser-visible domain. Mismatches often fail in the browser with little Laravel-side detail.
Clear stale challenge/session state between attempts. The v1.4.2 prompt fix is relevant if users report that only the first passkey prompt appears.
After config changes, clear/rebuild Laravel config cache and re-test the Filament panel.
Debug failures in both places: browser console/network for WebAuthn errors, and Laravel logs for credential persistence/auth guard issues.
v1.4.2 appears to be a patch release: no obvious breaking changes. The CI/package-standard change is contributor-facing; the prompt fix is the runtime behavior change worth validating after upgrade.
Extension points to check in the package source/config are the credential model/table, user resolver, Filament plugin registration, and any custom actions/pages for passkey management.