- What is n3xt0r/filament-passport-ui used for?
- It adds Filament v4/v5 admin resources for managing Laravel Passport OAuth clients, tokens, and scopes in a reviewable interface. It focuses on administration, visibility, and governance, not on implementing or enforcing OAuth flows. Use it when you already run Laravel, Passport, and Filament and want to replace CLI-only client management.
- Does filament-passport-ui implement OAuth flows or runtime authorization?
- No. It is an administrative and governance layer over Laravel Passport and does not enforce runtime authorization. Product and security stakeholders should not treat admin visibility as runtime control. Runtime enforcement must be handled elsewhere in the application.
- Which Laravel, PHP, Passport, and Filament versions are supported?
- It targets a bleeding-edge matrix: PHP 8.4/8.5, Laravel 12/13, Passport 13, and Filament 4/5. Treat version alignment as a go/no-go gate before committing. If the app is on older Laravel, Passport, or Filament versions, defer until an upgrade path exists.
- How do I install filament-passport-ui in a Laravel app?
- Install via Composer, then run the package install command, register the Filament plugin, and publish configuration if you need custom models. Migrations are supplied by the laravel-passport-authorization-core dependency. Test in a non-production environment first and back up Passport tables and activity logs.
- Can I use custom Passport client or token models with this package?
- Yes, configuration publication supports mapping custom Passport models, but custom models need explicit validation. Multi-panel Filament setups and multi-tenant ownership models also need validation. Confirm the UI and audit use cases cover your custom schema before production.
- How does auditability work in filament-passport-ui?
- Auditability depends on spatie/laravel-activitylog and application-owned logs. The package provides administrative actions through use cases that can be captured, but it does not make your organization compliant by itself. Direct database or CLI changes can bypass the UI audit trail, so block or document those workflows.
- Is filament-passport-ui production-ready for OAuth client management?
- It is technically feasible for a standard Passport installation, but the largest risks are maturity and low adoption, with 9 stars and 0 dependents suggesting limited community validation. Expect upgrade churn because it has already undergone a major v2 architectural split. Pin versions, test upgrades in staging, and pilot with one grant type before broad rollout.
- How should I handle scopes and migrate existing free-form scopes?
- Define a resource:action scope taxonomy before enabling client creation in the UI. Map existing free-form scopes to the new taxonomy and pilot with one grant type, ideally client credentials or authorization code. The package helps you manage scopes, but migration is an application governance decision.
- What alternatives exist to using a Filament admin UI for Laravel Passport?
- You can keep Passport's CLI workflows, build custom admin tooling, or use this package if you already standardize on Filament. The package is best suited to teams replacing CLI-only OAuth client management with a reviewable admin workflow. If you do not already use Filament as your admin panel, it is not a good fit.
- How do I test and maintain filament-passport-ui given its low adoption?
- Run a version and architecture spike in staging, then install the package and core dependency against a production-like schema copy. Configure custom models, panel access, policies, and scope taxonomy before piloting with a controlled admin group. Pin package versions, require changelog review before upgrades, and plan for single-maintainer support risk.