Weave Code
Laravel Jetstream Passport Laravel Package
headerx/laravel-jetstream-passport
Integrates Laravel Passport with Jetstream to add OAuth2 API token management to your Inertia/Vue app. Provides ready-made UI for creating, viewing, and revoking personal access tokens and managing API clients alongside Jetstream's existing profile features.
Passport and OAuth2 support for Laravel's Jetstream starter kit (Livewire)
Frequently asked questions about Laravel Jetstream Passport
- How do I install headerx/laravel-jetstream-passport in a Laravel Jetstream app?
- Install it with Composer and follow the package service provider and configuration publishing steps. The provided evaluation does not include a full README, so confirm the exact migration, Passport client, and asset publishing commands in the repository before rolling it out.
- Does this package work with Jetstream Livewire or Inertia/Vue?
- The package overview describes Passport and OAuth2 support for Laravel Jetstream's Livewire starter kit, while the blurb references an Inertia/Vue app. The technical evaluation explicitly flags this as an open question, so confirm which Jetstream stack your installation uses before adopting it.
- Do I need to disable Laravel Sanctum to use Passport with Jetstream?
- Not necessarily, but you must plan guard and middleware boundaries carefully. Jetstream defaults to Sanctum, so introducing Passport creates dual token systems; the evaluation notes that installation should document whether Sanctum is disabled or run side by side.
- How do I customize the OAuth2 authorization or consent screen?
- The v1.0.2 release adds an authorize view, which is the consent screen Passport integrations often force teams to fork. Check whether that view publishes to resources/views/vendor so you can override branding and consent copy without forking the package itself.
- Which Laravel, Jetstream, and Passport versions are supported?
- The provided evaluation does not list composer.json constraints for laravel/framework, laravel/jetstream, or laravel/passport. Check the repository composer.json and CI matrix before assuming support for the Laravel and Jetstream majors you run today.
- Can I manage OAuth2 clients and personal access tokens from the Jetstream UI?
- Yes. The package is intended to provide ready-made Jetstream UI for creating, viewing, and revoking personal access tokens and managing API clients alongside Jetstream's existing profile features.
- Is this package suitable for an existing app already using Sanctum tokens?
- The evaluation recommends treating it as greenfield-only for the auth layer in v1. Adopting it on an app with live Sanctum tokens means token migration and a guard cutover, which is a multi-sprint change with user-visible re-authentication.
- Which OAuth2 flows does this package support?
- The package bridges Jetstream to Laravel Passport, so the available flows are those Passport supports, including authorization code with PKCE, client credentials, and personal access tokens. The package itself is an integration layer rather than a replacement OAuth2 server.
- Is headerx/laravel-jetstream-passport tested and actively maintained?
- The provided evaluation does not include test coverage, CI status, maintainer count, or install-base data. It also flags ad-hoc release discipline, including a view added in a patch release and v1.0.1 missing from the changelog, so ask for the CI matrix and maintenance plan before production adoption.
- What are alternatives to this package for adding OAuth2 to Laravel Jetstream?
- If you only need first-party SPA or mobile tokens, Sanctum alone is lighter and this package is unnecessary scope. If you need OAuth2 authorization-code flow with third-party clients, using Laravel Passport directly or this Jetstream integration are the main options; compare the glue code you would otherwise write.
Weaver
How can I help you explore Laravel packages today?