Download the PHP package imanrjb/passport-auth without Composer
On this page you can find all versions of the php package imanrjb/passport-auth. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download imanrjb/passport-auth
More information about imanrjb/passport-auth
Files in imanrjb/passport-auth
Package passport-auth
Short Description Laravel and Lumen passport package
License MIT
Informations about the package passport-auth
Passport Auth
Making Laravel Passport work with Lumen
A simple service provider that makes Laravel Passport work with Lumen
Dependencies
- PHP >= 8.0
- Lumen >= 9.0
Installation via Composer
Or if you prefer, edit composer.json
manually:
Modify the bootstrap flow ( file)
Registering Routes
Next, you should call the LumenPassport::routes method within the boot method of your application (AuthServiceProvider.php). This method will register the routes necessary to issue access tokens and revoke access tokens, clients, and personal access tokens:
You can add that into an existing group, or add use this route registrar independently like so;
Migrate and install Laravel Passport
Installed routes
This package mounts the following routes after you call routes() method (see instructions below):
Verb | Path | NamedRoute | Controller | Action | Middleware |
---|---|---|---|---|---|
POST | /oauth/token | \Laravel\Passport\Http\Controllers\AccessTokenController | issueToken | - | |
GET | /oauth/tokens | \Laravel\Passport\Http\Controllers\AuthorizedAccessTokenController | forUser | auth | |
DELETE | /oauth/tokens/{token_id} | \Laravel\Passport\Http\Controllers\AuthorizedAccessTokenController | destroy | auth | |
POST | /oauth/token/refresh | \Laravel\Passport\Http\Controllers\TransientTokenController | refresh | auth | |
GET | /oauth/clients | \Laravel\Passport\Http\Controllers\ClientController | forUser | auth | |
POST | /oauth/clients | \Laravel\Passport\Http\Controllers\ClientController | store | auth | |
PUT | /oauth/clients/{client_id} | \Laravel\Passport\Http\Controllers\ClientController | update | auth | |
DELETE | /oauth/clients/{client_id} | \Laravel\Passport\Http\Controllers\ClientController | destroy | auth | |
GET | /oauth/scopes | \Laravel\Passport\Http\Controllers\ScopeController | all | auth | |
GET | /oauth/personal-access-tokens | \Laravel\Passport\Http\Controllers\PersonalAccessTokenController | forUser | auth | |
POST | /oauth/personal-access-tokens | \Laravel\Passport\Http\Controllers\PersonalAccessTokenController | store | auth | |
DELETE | /oauth/personal-access-tokens/{token_id} | \Laravel\Passport\Http\Controllers\PersonalAccessTokenController | destroy | auth |
Please note that some of the Laravel Passport's routes had to 'go away' because they are web-related and rely on sessions (eg. authorise pages). Lumen is an API framework so only API-related routes are present.
User model
Make sure your user model uses Passport's trait, eg.:
Different TTLs for different password clients
Laravel Passport allows to set one global TTL for access tokens, but it may be useful sometimes to set different TTLs for different clients (eg. mobile users get more time than desktop users).
Simply do the following in your service provider:
If you don't specify client Id, it will simply fall back to Laravel Passport implementation.
Console command for purging expired tokens
Simply run to remove expired refresh tokens and their corresponding access tokens from the database.
Issue token
Refresh token
All versions of passport-auth with dependencies
hisorange/browser-detect Version ^4.4
nyholm/psr7 Version ^1.5
imanrjb/lumen-vendor-publish Version ^1.0