Filament Socialite Laravel Package

Product Decisions This Supports

• Feature: social login for Filament panels. This release makes "Sign in with Google/GitHub/etc." a configurable, per-panel capability rather than custom Socialite wiring. Directly supports signup/login conversion work: fewer passwords created, fewer reset flows, shorter time-to-first-value for B2C-facing panels (customer portals, SaaS dashboards, member areas).
• Roadmap: Filament v4 upgrade. 2.0.0 is explicitly the first Filament v4-compatible release. If the v4 migration is on the roadmap, this package moves from "blocked" to "available" — it is a dependency-unblock signal, not a feature bet.
• Build vs. buy: lean adopt. The delivered surface (provider config object, panel-scoped routes, login-form hook injection, optional registration with createUserUsing / resolveUserUsing / canAccessPanel() hooks) is roughly 1–3 days of engineering to replicate well, plus ongoing maintenance. Buying is the cheaper call if the vendor risk is acceptable.
• Use cases that fit: consumer/member logins on a Filament panel; reducing friction for invited users; panels where the same human logs in repeatedly and password fatigue hurts retention.
• Use cases that do NOT fit: enterprise SSO (SAML, IdP-initiated OIDC, SCIM provisioning) — OAuth login buttons are not workforce identity; social login for non-panel surfaces (public marketing site, mobile app, API clients) — this is panel-scoped; environments requiring vendor SLAs or a security review process.

Caveat on evidence: this assessment is derived from 2.0.0 release notes only. No code audit, no adoption data, no security posture review. Treat capability claims as vendor-stated until validated in a spike.

When to Consider This Package

Consider it when:

• You are on Filament v4 (2.0.0 is v4-only — confirm your version before scoping).
• Social login is a nice-to-have conversion lever, not a regulated identity requirement.
• Your user records already exist or are created through a path you control — the resolveUserUsing / createUserUsing callbacks give you a seam to keep account-linking logic in your domain.
• You want the login buttons to be per-panel and themeable (label, icon, color, scopes, extra params, stateless) without patching Filament's auth views.
• You need pt-BR or English UI out of the box, or the hook-based customization (AUTH_LOGIN_FORM_AFTER) is enough for your design.
• A small team owns the panel and can absorb a single-maintainer dependency.

Look elsewhere when:

• You need enterprise SSO. Different product category; evaluate a SAML/OIDC identity broker instead.
• You are still on Filament v3 — 2.0.0 will not install. Check whether a 1.x line is maintained, and for how long.
• You need social login outside a Filament panel (public site, API, mobile). Use Laravel Socialite directly.
• Supply-chain or procurement scrutiny applies. This package delegates account linking to jeffersongoncalves/laravel-socialite, another single-maintainer package. Two hops of individual ownership, no visible security policy or LTS commitment. If your org requires maintainer-diversity or CVE response SLAs, this fails the bar.
• Open registration is a concern. Optional registration plus a canAccessPanel() check means misconfiguration can create accounts that reach a panel. If you cannot guarantee the check is wired, defer.
• You need control over email-collision and unverified-email account-merging edge cases. The callbacks let you implement this, but you will be writing it — budget for it rather than assuming it is handled.
• Callback URLs behind reverse proxies, custom domains, or multi-tenant subdomains need validation; auto-generated callback URLs are convenient but must be verified per environment.

How to Pitch It (Stakeholders)

For executives: Social login is a low-cost conversion and retention lever — users who sign in with an existing identity skip password creation and reset. This release makes it a configuration task on our admin/customer panel rather than a custom build, and it unblocks our Filament v4 upgrade. Cost is minimal; the main risk is vendor concentration, since the plugin and its account-linking dependency are both maintained by individual developers. Recommendation: adopt behind a feature flag, instrument login-method mix and signup completion, and re-evaluate at the next major Filament release. Do not position this as enterprise SSO — it is consumer-style social login only.

For engineering: It is a thin Filament plugin over Laravel Socialite. It registers redirect/callback routes per panel, generates callback URLs, injects buttons via AUTH_LOGIN_FORM_AFTER, and exposes a fluent Provider value object (label, icon, color, scopes, extra params, stateless). Registration is opt-in, with createUserUsing / resolveUserUsing / canAccessPanel() as the extension points — that is where your account-linking, email-verification, and authorization policy belongs. Before enabling: pin both packages, audit the callback route registration and middleware, confirm registration is off by default in your config, test callback URL generation behind the proxy, and write explicit tests for the email-collision path. Treat the v4 requirement as a hard gate — this is a major-version jump tied to Filament's own major, so plan the upgrade in lockstep.