- How do I install filament-socialite in my Laravel Filament v4 panel?
- Require the package with Composer, then publish its configuration file so you can define your providers. Register the SocialitePlugin in your panel provider's plugin() method, which is the standard Filament v4 extension pattern. Finally, add the client_id, client_secret, and redirect values for each provider to your .env file and clear your config cache.
- Which social providers does this package support?
- It works with any Laravel Socialite provider, so Google, GitHub, and Facebook are available out of the box along with the other drivers Socialite ships. Because it is a thin orchestration layer, custom drivers registered through Socialite::extend should also work. You still need to register the OAuth application and consent screen with each provider yourself.
- How do I configure the social login buttons and their icons?
- Providers are declared with a fluent Provider API in the plugin registration, where you set the provider name, label, icon, and any redirect behavior. The buttons are rendered through Filament's AUTH_LOGIN_FORM_AFTER render hook on both the login and registration pages. Because placement depends on that hook, a Filament minor release that renames or reorders it could shift your buttons, so re-check the UI after upgrading Filament.
- Does this package support Laravel 12 and Filament v4?
- Version 2.0.0 is the first release targeting Filament v4, and the major version numbers track Filament's, meaning v1.x was built for Filament v3. The exact PHP and Laravel constraints are defined in composer.json, so check those before installing on an older or very new Laravel release. Pin an exact version and treat minor bumps as reviewable changes, since v2 is early in its lifecycle.
- How are users created or linked when someone signs in with Google or GitHub?
- The plugin delegates account creation and matching to jeffersongoncalves/laravel-socialite, exposing resolveUserUsing and createUserUsing callbacks so you can control the logic. If you are replacing a hand-rolled Socialite controller, this is where most of your migration effort goes. Before going live, confirm whether your resolveUserUsing callback requires a provider-verified email, since matching on an unverified address is an account-takeover risk.
- Can different Filament panels show different social providers?
- Yes. Routes and callback URLs are generated per panel, so an admin panel and a customer-facing panel can expose different provider sets without route collisions. The trade-off is that callback URLs are derived from panel routing state, which is a common source of misconfiguration between local, staging, and production. Verify the generated URL for each panel in each environment.
- How do I test social login without hitting the real provider?
- Mock the Socialite driver in your test suite so the redirect and callback flows return a fake user instead of contacting Google or GitHub. Then assert that a user is created on first login, that an existing user is matched on subsequent logins, and that a user denied panel access is rejected. Also test the callback with a mismatched or missing state parameter if you rely on state validation.
- Is social login safe to enable on an admin panel?
- The package supports optional registration gated by Filament's canAccessPanel() check, which is what makes social login viable for admin panels, where authenticating with Google must not imply gaining access. Confirm that the check is enforced during the login callback and not only when rendering the button. Also avoid the stateless provider flag on a web login form, since it disables OAuth state validation.
- What redirect and callback URLs do I register in my OAuth app?
- The plugin registers redirect and callback routes for each panel and provider, so copy the exact URL it generates into the provider's console. Mismatches between the registered URL and the one generated in a given environment are the most frequent cause of failed callbacks. Remember that changing your panel path or domain changes the callback URL, so update the provider configuration alongside it.
- What are the alternatives to filament-socialite?
- You can hand-roll a Socialite button and controller inside your own Filament login view, or use another Filament social login plugin. This package is a narrow UI and orchestration layer over Socialite rather than a replacement, and its account-linking behavior lives in a companion package under a personal namespace. Choose it if you want declarative per-panel configuration and are comfortable that your auth path's release cadence and test coverage follow those two packages.