- How do I install filament-oidc in a Laravel app with a Filament panel?
- Install it with Composer using the package name jeffersongoncalves/filament-oidc, then publish its config and migration tags. Because version 3.1.0 extracts identity persistence into jeffersongoncalves/laravel-oidc, that core package is pulled in as a hard runtime dependency. Run your migrations and wire the plugin into your Filament panel provider so the login page can hand off to the OIDC provider.
- Which OIDC providers are supported by filament-oidc?
- Any OpenID Connect compliant provider works, since the package relies on standard OIDC discovery rather than provider-specific code. Common choices include Keycloak, Auth0, Azure AD, Okta, and Authentik. You only need to supply the issuer URL and client credentials, and the endpoints and signing keys are resolved from the discovery document.
- How does automatic user provisioning work with claim mapping?
- When a user returns from the provider, the package matches the OIDC identity by issuer and subject and creates or links a local user record. Claim mapping is configurable, so you decide which ID token or userinfo claims populate fields such as name and email. The OidcIdentity model and HasOidcIdentities trait now live in the shared laravel-oidc core package, so identity records are reusable outside Filament panels.
- Does filament-oidc support Laravel 11 and Filament 3?
- The package is built as a Filament 3 panel integration, so it targets current Filament v3 applications rather than Filament 2. Exact PHP and Laravel constraints are declared in its composer.json, and you should check those before installing. Note that 3.1.0 also requires jeffersongoncalves/laravel-oidc in the 1.3 line, which may carry its own minimum framework versions.
- What changed in filament-oidc 3.1.0 and how do I upgrade safely?
- Version 3.1.0 is a refactor that moves identity storage into jeffersongoncalves/laravel-oidc, producing four mechanical renames: the OidcIdentity model and HasOidcIdentities trait namespaces, the config key filament-oidc.identities_table to oidc.identities_table, and the migration publish tag filament-oidc-migrations to oidc-migrations. The table name and schema are unchanged, so no data migration or backfill is needed, but any of your own code reading the old config key will silently return null. Update use statements, config reads, and deployment scripts before deploying.
- How do I publish the config file and migrations for filament-oidc?
- Use Laravel's vendor:publish command with the package's publish tags. In 3.1.0 the migration tag changed from filament-oidc-migrations to oidc-migrations, and the config key prefix moved from filament-oidc to oidc, so update any runbooks or CI scripts that reference the old tags. If you upgrade from 3.0.x, previously published migrations continue to work unchanged.
- Can I use OIDC login outside a Filament panel, for example in an API?
- Yes. As of 3.1.0 the OidcIdentity model and HasOidcIdentities trait are provided by the framework-agnostic jeffersongoncalves/laravel-oidc package, while filament-oidc is a thin UI layer on top. That means you can add OIDC authentication to other Laravel surfaces, such as a separate admin area or API guard, using the core package directly. Just keep the two packages' versions compatible, since the constraint between them is maintained by hand.
- How do I test OIDC login in a Laravel application using filament-oidc?
- Because the login flow depends on an external identity provider, feature tests should fake the OIDC responses rather than hitting the real provider. Assert the callback path, the identity matching by issuer and subject, and that a local user is created or linked on first login. Also cover the failure paths, such as an invalid state or mismatched nonce, since a defect here can mean either a lockout or an authentication bypass.
- Is filament-oidc safe to use for a production admin panel?
- It is usable in production, but treat upgrades as security-relevant changes rather than routine dependency bumps, because this plugin gates admin panel access. Version 3.1.0 shipped a breaking rename in a minor release, so pin exact versions instead of using caret ranges, and roll out changes through staging first. Both filament-oidc and laravel-oidc are single-maintainer packages, which is worth weighing for supply chain and bus factor risk.
- What are alternatives to filament-oidc for Filament single sign-on?
- You can build OIDC login yourself with Laravel Socialite plus a generic OIDC client, or use the underlying jeffersongoncalves/laravel-oidc package if you want the identity model without the Filament plugin. Other options include Fortify with a custom guard and a standards-compliant OIDC library, or a hosted identity broker that presents a simpler protocol. filament-oidc remains the most direct route if you specifically want discovery-based OIDC inside a Filament panel.