- How do I install Socialment in a Laravel Filament app?
- Install with composer require chrisreedio/socialment, then run php artisan socialment:install. You must add a Tailwind @source line for the package resources to a custom Filament theme and register SocialmentPlugin::make() in your PanelProvider. The @source step is mandatory for correct button styling.
- Why are my Socialment OAuth buttons not showing or unstyled?
- Usually the package Tailwind source path is missing from your custom Filament theme. Add @source '../../../../vendor/chrisreedio/socialment/resources' to the theme CSS and rebuild assets. Without a compiled custom theme the buttons can render unstyled or invisible, and this failure is silent rather than an error.
- Does Socialment support Filament v4?
- Socialment targets the Filament v3 and v4 lines, with v4 current and v3 prior. The demo project is not yet updated to v4, so confirm the v4 path is exercised in real applications. Version constraints are deliberately loose, so compatibility verification is partly your responsibility.
- How do I configure Socialite providers, icons, and per-panel settings in Socialment?
- Put provider credentials in config/services.php and call registerProvider($name, $icon, $label) on the Socialment plugin in your PanelProvider. For community providers, also add the standard SocialiteWasCalled listener. Configuration is per panel, so each Filament PanelProvider can register its own providers, icons, and labels. This mirrors Laravel Socialite wiring, so existing Socialite knowledge transfers directly.
- What are the alternatives to Socialment for Filament OAuth login?
- The main alternative is wiring Laravel Socialite directly and rendering custom OAuth buttons on the Filament login page. Socialment is deliberately a thin adapter, so a small custom plugin is a reasonable option if you need more control or a fork you own. Choose based on whether you want convenience now or full control over the authentication boundary.
- Does Socialment automatically link a Socialite login to an existing user by email?
- The package links a Socialite identity to an existing User through its ConnectedAccount model, but the email-collision policy is not clearly specified in the docs. You must determine whether a matching identity provider email auto-links, refuses, or creates a duplicate account. This is the highest-severity unknown because auto-linking can become an account-takeover vector.
- Are Socialite access and refresh tokens encrypted at rest by Socialment?
- The docs show the token attribute being passed to provider clients, but they do not clearly promise encryption at rest. Confirm the ConnectedAccount casts and database column encryption before production. If tokens are stored in plaintext, add encryption or avoid persisting them.
- What callback URL does Socialment use with multiple Filament panels or custom panel paths?
- The documentation asserts /login/{provider}/callback, but that may change under a prefixed panel slug or with multiple panels. Test the actual redirect URI in your panel configuration before registering it with each identity provider. A mismatch will cause OAuth callback failures.
- Is the SPA authentication feature in Socialment production ready?
- No. The SPA authentication feature is self-labeled highly experimental, subject to breaking changes, and possibly split into a separate package. Scope it out of production plans. If you need shared SPA and panel sessions, solve it natively with Sanctum stateful domains.
- Is Socialment well tested and safe for production authentication?
- Treat coverage as unverified: the README says tests have yet to be written, which conflicts with the green test and PHPStan badges. Adoption is low at 109 stars and zero dependents, with a single primary maintainer. It is reasonable for internal staff panels, but customer-facing auth needs a written fork-and-own plan and pre-adoption tests on callback and account-linking paths.