n3xt0r/filament-passport-ui

Filament admin UI for managing Laravel Passport OAuth clients, tokens, and scopes.

dev-main 2025-12-31 02:15 UTC

Requires

• php: ^8.4
• filament/filament: ^4.0
• laravel/passport: ^13.0
• spatie/laravel-activitylog: ^4.0
• spatie/laravel-package-tools: ^1.15.0

Requires (Dev)

• larastan/larastan: ^3.0
• laravel/pint: ^1.0
• nunomaduro/collision: ^8.0
• orchestra/testbench: ^10.0
• phpstan/extension-installer: ^1.1
• phpstan/phpstan-deprecation-rules: ^2.0
• phpstan/phpstan-phpunit: ^2.0
• phpunit/phpunit: ^12.5
• rector/rector: ^2.0
• spatie/laravel-ray: ^1.26

MIT

• Ilya Beliaev

• laravel
• N3XT0R
• laravel-passport
• filamentphp
• filament-passport-ui
• passport-ui

README

Filament admin UI for managing Laravel Passport OAuth clients, tokens, and scopes.

This package provides a clean, opinionated Filament integration for Laravel Passport, allowing OAuth-related resources to be managed directly from the Filament admin panel instead of via CLI commands or static configuration.

It is intended for applications that already use Filament as their primary admin interface and want first-class Passport administration without maintaining custom internal tooling.

Features

• Manage OAuth clients (personal access, password, client credentials)
• View and revoke access tokens
• Manage scopes via UI (optionally database-driven)
• Native Filament v4 Resources & Pages
• No modifications to Passport internals
• Works with existing Passport installations

This package focuses on administration, not authentication flows.

Why this exists

Laravel Passport provides a solid and standards-compliant OAuth2 implementation.
It intentionally focuses on protocol mechanics and leaves administrative concerns to the application.

In practice, this often leads to recurring problems:

• OAuth clients are created once via CLI and then forgotten
• Client ownership is unclear, especially for client_credentials grants
• Scopes are either not used at all or defined ad-hoc in code without structure
• There is no central place to review, manage, or reason about OAuth configuration

This package exists to fill that gap.

Filament Passport UI adds an administrative and domain-oriented layer on top of Laravel Passport, without changing its behavior or assumptions. It does not replace Passport, nor does it attempt to redefine OAuth flows. Instead, it provides structure, visibility, and responsibility where Passport intentionally remains neutral.

Key principles behind this package:

• OAuth clients should have explicit ownership
• Scopes should be composable, understandable, and centrally managed
• Administrative actions should be visible, reviewable, and auditable
• OAuth configuration should be manageable without embedding governance logic in application code

By integrating with Filament, this package offers a practical and predictable way to manage OAuth clients and scopes in real-world applications, especially in systems with multiple integrations, services, or teams.

Requirements

• PHP ^8.4
• Laravel ^12
• Laravel Passport
• Filament v4

Installation

Install the package via Composer:

composer require n3xt0r/filament-passport-ui

php artisan filament-passport-ui:install
``