Download the PHP package yuanchang/lumen-passport without Composer
On this page you can find all versions of the php package yuanchang/lumen-passport. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download yuanchang/lumen-passport
More information about yuanchang/lumen-passport
Files in yuanchang/lumen-passport
Package lumen-passport
Short Description Making Laravel Passport work with Lumen
License MIT
Informations about the package lumen-passport
lumen-passport
Making Laravel Passport work with Lumen
A simple service provider that makes Laravel Passport work with Lumen
Feature
- support passport
- support mobile grant
Dep
- PHP >= 5.6.3
- Lumen >= 5.3
Or edit composer.json
manually:
Modify the bootstrap flow ( file)
We need to enable both Laravel Passport provider and Lumen-specific provider:
If you want use mobile grant type and you want custom verify mobile validate type.
you need implement MobileChecker interface.
if you implement MobileChecker, you need extendMobileChecker
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.
Configuration
Edit config/auth.php to suit your needs. A simple example:
Load the config in bootstrap/app.php
since Lumen doesn't load config files automatically:
Registering Routes
Next, you should call the LumenPassport::routes method within the boot method of your application (one of your service providers). 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;
User model
Make sure your user model uses Passport's trait, eg.:
Extra features
There are a couple of extra features that aren't present in Laravel Passport
Allowing multiple tokens per client
Sometimes it's handy to allow multiple access tokens per password grant client. Eg. user logs in from several browsers simultaneously. Currently Laravel Passport does not allow that.
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.
Running with Apache httpd
If you are using Apache web server, it may strip Authorization headers and thus break Passport.
Add the following either to your config directly or to :
License
The MIT License (MIT) Copyright (c) 2016 Denis Mysenko
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
All versions of lumen-passport with dependencies
illuminate/database Version ~5.3|~5.4|~5.5|~5.6
illuminate/support Version ~5.3|~5.4|~5.5|~5.6
laravel/passport Version >=0.2.2