[13.x] Make Passport headless (Support Laravel Jetstream and Breeze)

[hafezdivandari]

• Requires [13.x] Make client RFC compatible #1744

Passport has a view for authorization / consent, this view doesn't load correctly for many years (maybe since Mix / Bootstrap CSS are not installed on Laravel Skeleton by default). Also more views are needed for Device flow (#1750), makes user experience even worse!

This PR makes Passport headless just like Fortify because Passport doesn't have any pre-installed UI scaffolding. Therefore, we add support for Jetstream and Breeze that already have UI for different stacks:

• Laravel Jetstream: [5.x] Support Laravel Passport jetstream#1521
• Laravel Breeze: [2.x] Support Laravel Passport breeze#398
• Laravel UI: I have the PR ready for Laravel UI but OAuth option seems to be confusing for Laravel UI? as it doesn't call install:api during installation unlike Jetstream and Breeze. Let me know if you want a PR for this.

Changes

• Makes Passport headless.
  • New Passport::viewPrefix() method (inspired by Fortify).
  • New Passport::viewNamespace() (inspired by Fortify).
• Add new methods to be compatible with Jetstream and interchangable with Sanctum:
  • New Passport::defaultScopes() method.
  • New Passport::validScopes() method.
  • New User::currentAccessToken() as an alias for User::token() to be interchange with Sanctum.
• Fix view response and rename it to SimpleViewResponse (inspired by Fortify), to be generic for the future views.
• Fix Client::firstParty() method. We consider a client first-party when it doesn't belong to any user.

[github-actions]

Thanks for submitting a PR!

Note that draft PR's are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface.

Pull requests that are abandoned in draft may be closed due to inactivity.

[hafezdivandari]

Hi @driesvints sorry to bother you, I just wanted to ask your opinion before continuing my work on this.

I'm gonna add a passport:ui artisan command that installs stubs based on user UI preferences. Also I'm gonna add support for Jetstream "API Token Manager". What do you think?

[driesvints]

Hey @hafezdivandari. That seems fine for us! Thank you so much for all your work on this 👏

[inmanturbo]

@hafezdivandari You've done a great deal of solid work on this throughout the ecosystem and it's much appreciated.

I maintain some custom in house sso servers for a handleful of privately owned businesses, and they all use Passort for oauth. They are all running on forge provisioned servers and so we try keep them up to date to stay in line with current forge offerings.

In the past the way to use passport with something like breeze or jetstream was to publish the view and modify to our needs, or otherwise place our own stub in the resources/views/vendor/passport/authorize.blade.php.

How would this change affect these existing applications?

[hafezdivandari]

Thank you @inmanturbo

When the view is on the resources/views/vendor/passport/authorize.blade.php path, Passport::viewNamespace('passport') should do the work.

As stated on the PR description, more views are comming for the new device flow. Each view will have its own method to render the view (just like Fortify) e.g Passport::authorizationView(), useful for Inertia stack. Also Passport::viewPrefix() and Passport::viewNamespace() helper methods are available to set the path for all views, useful for Livewire stack.

You may also check the upgrade guide entry for more info.