Download the PHP package dusterio/lumen-passport without Composer
On this page you can find all versions of the php package dusterio/lumen-passport. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download dusterio/lumen-passport
More information about dusterio/lumen-passport
Files in dusterio/lumen-passport
Package lumen-passport
Short Description Making Laravel Passport work with Lumen
License MIT
Homepage https://github.com/dusterio/lumen-passport
Informations about the package lumen-passport
Lumen Passport
Making Laravel Passport work with Lumen
Introduction
It's a simple service provider that makes Laravel Passport work with Lumen.
Installation
First install Lumen Micro-Framework if you don't have it yet.
Then install Lumen Passport:
Or if you prefer, edit composer.json
manually and run then composer update
:
Modify the bootstrap flow
We need to enable both Laravel Passport provider and Lumen Passport specific provider:
Laravel Passport ^7.3.2 and newer
On 30 Jul 2019 Laravel Passport 7.3.2 had a breaking change - new method introduced on Application class that exists in Laravel but not in Lumen. You could either lock in to an older version or swap the Application class like follows:
* Note: If you look inside this class - all it does is adding an extra method configurationIsCached()
that always returns false
.
Migrate and install Laravel Passport
It will output the Personal access client ID and secret, and the Password grand client ID and secret.
* Note: Save the secrets in a safe place, you'll need them later to request the access tokens.
Configuration
Configure Authentication
Edit config/auth.php
to suit your needs. A simple example:
* Note: Lumen 7.x and older uses \App\User::class
Load the config 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:
User model
Make sure your user model uses Laravel Passport's HasApiTokens
trait.
Usage
You'll find all the documentation in Laravel Passport Docs.
Curl example with username and password authentication
First you have to issue an access token and then you can use it to authenticate your requests.
And with the access_token
you can request access to the routes that uses the Auth:Api Middleware provided by the Lumen Passport.
Installed routes
This package mounts the following routes after you call routes()
method, all of them belongs to the namespace \Laravel\Passport\Http\Controllers
:
Verb | Path | Controller | Action | Middleware |
---|---|---|---|---|
POST | /oauth/token | AccessTokenController | issueToken | - |
GET | /oauth/tokens | AuthorizedAccessTokenController | forUser | auth |
DELETE | /oauth/tokens/{token_id} | AuthorizedAccessTokenController | destroy | auth |
POST | /oauth/token/refresh | TransientTokenController | refresh | auth |
GET | /oauth/clients | ClientController | forUser | auth |
POST | /oauth/clients | ClientController | store | auth |
PUT | /oauth/clients/{client_id} | ClientController | update | auth |
DELETE | /oauth/clients/{client_id} | ClientController | destroy | auth |
GET | /oauth/scopes | ScopeController | all | auth |
GET | /oauth/personal-access-tokens | PersonalAccessTokenController | forUser | auth |
POST | /oauth/personal-access-tokens | PersonalAccessTokenController | store | auth |
DELETE | /oauth/personal-access-tokens/{token_id} | PersonalAccessTokenController | destroy | auth |
* Note: 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.
Extra features
There are a couple of extra features that aren't present in Laravel Passport
Prefixing Routes
You can add that into an existing group, or add use this route registrar independently like so;
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 (time to live) 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.
Purge expired tokens
Simply run it to remove expired refresh tokens and their corresponding access tokens from the database.
Error and issue resolution
Instead of opening a new issue, please see if someone has already had it and it has been resolved.
If you have found a bug or want to contribute to improving the package, please review the Contributing guide and the Code of Conduct.
Video tutorials
I've just started a educational YouTube channel config.sys that will cover top IT trends in software development and DevOps.
Also I'm happy to announce my newest tool – GrammarCI, an automated (as a part of CI/CD process) spelling and grammar checks for your code so that your users don't see your typos :)
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|^6.0|^7.0|^8.0|^9.0|^10.0
illuminate/support Version ~5.3|~5.4|~5.5|~5.6|^6.0|^7.0|^8.0|^9.0|^10.0
laravel/passport Version >=0.2.2
laminas/laminas-diactoros Version ^2.4