Weave Code
Filament Keycloak Admin Laravel Package
sandstorm/filament-keycloak-admin
Filament Keycloak Admin brings Keycloak identity management into your Laravel Filament panel, providing a familiar interface to browse and administer realms, users, roles, and groups without switching tools. Ideal for teams that want streamlined admin workflows and fewer context switches.
At a glance
Frequently asked questions about Filament Keycloak Admin
- What is sandstorm/filament-keycloak-admin used for?
- It brings Keycloak identity management into Laravel Filament admin panels so teams can browse and administer realms, users, roles, and groups without switching tools. It is aimed at Laravel applications that delegate authentication to Keycloak-backed SSO and want streamlined admin workflows.
- Which Laravel and PHP versions are supported by filament-keycloak-admin?
- The provided v1.2.0 release notes do not list supported Laravel or PHP versions. Check the repository composer.json, README, and dependency constraints before installing, and verify compatibility in a sandbox. Do not assume compatibility solely because v1.2.0 is a minor release.
- How do I install and configure sandstorm/filament-keycloak-admin in a Laravel Filament panel?
- Use Composer with the package name sandstorm/filament-keycloak-admin, then follow the package README for Filament panel registration, configuration publishing, and Keycloak realm/client credentials. The assessment did not include full installation documentation, so review the source and config before production. Start in a non-critical Laravel service or staging environment.
- Does filament-keycloak-admin replace Keycloak or handle SSO authentication itself?
- No, it integrates with Keycloak HTTP APIs and provides a Filament admin interface for Keycloak identity objects. Authentication is delegated to an external SSO provider, with Keycloak as the identity system. Review the package source to confirm the exact login, logout, callback, and token-refresh flows for your setup.
- What changed in filament-keycloak-admin v1.2.0?
- v1.2.0 adds extension points for audit logging and HTTP trace logging, which support compliance, incident response, and production observability. It also adds UI error messages for SSO authentication failures and Keycloak API errors. The minor version suggests backward compatibility, but verify the changelog and dependency resolution before upgrading.
- Are the audit and HTTP trace extension points stable interfaces covered by semantic versioning?
- The provided release notes do not define the extension-point contracts or state whether they are interfaces, Laravel events, or middleware. Inspect the source and confirm whether those APIs are covered by semantic versioning before relying on them. Treat any custom audit or trace integration as code that needs regression testing on package upgrades.
- Do the audit and HTTP trace logs redact tokens, assertions, cookies, and PII by default?
- The assessment does not state default redaction behavior for the new audit and HTTP trace logging extension points. Treat redaction, retention, access control, and log-volume limits as required production review items. Wire logs into approved sinks and test that sensitive authentication data is not captured.
- Are the new SSO and Keycloak API error messages safe and localizable for end users?
- v1.2.0 improves UI error messages for SSO authentication failures and Keycloak API errors, but safety and localization details are not documented in the assessment. Review the messages to ensure they do not expose tokens, certificates, realm or client details, or internal network information. Support runbooks should map user-facing messages to Keycloak configuration and API failure causes.
- How should I test filament-keycloak-admin before using it in production?
- Sandbox-install the package with a test Keycloak realm and client, then exercise successful SSO, failed SSO, Keycloak HTTP failure, logout, token refresh, and audit/trace logging paths. If replacing a manual Keycloak integration, establish parity for login, callback, error handling, and audit events before cutover. Run a security and privacy review of logs and error UI, then pilot in staging with a rollback plan.
- How does filament-keycloak-admin compare with alternatives, and is it actively maintained?
- Alternatives include direct Keycloak Admin REST API calls, custom Filament resources, or other Keycloak admin packages. This package fits teams already using Laravel, Filament, and Keycloak-backed SSO, especially when audit and HTTP trace hooks matter. The provided assessment covers only v1.2.0 release notes, so check repository commits, releases, issues, license, and maintenance cadence before adoption.
Weaver
How can I help you explore Laravel packages today?