Download the PHP package leadout/jwt without Composer
On this page you can find all versions of the php package leadout/jwt. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package jwt
leadout-jwt
A lightweight JWT guard for Laravel.
Installation
Install the package through composer:
The package will automatically register the authentication guard.
Configuration
Configuring the package takes place solely through the guard configuration in Laravel's native auth.php configuration file.
The following example shows all the configuration that can be passed to the guard:
The provider should be defined in the providers array in the authentication configuration file.
The key is used for encoding and decoding the tokens and should be kept secret.
If not using a single key for both encoding and decoding, the public_key and private_key should point to the public and private keys that are used for encoding and decoding the tokens.
The ttl value is the time-to-live for the token in minutes. This field can be omitted from the config. If omitted, the default time-to-live for tokens is set to 60 minutes.
Additional claims that should be added to all tokens issued through the guard should be added to the claims configuration. This configuration key can be omitted.
Usage
Since the guard is purely configured through Laravel's native auth configuration, it is recommended only instantiating it through the auth manager:
Attempting to authenticate a user
It is possible to authenticate a user given the credentials for that user. If a user cannot be authenticated with the credentials, null is returned.
The attempt method mimics the way that the native SessionGuard attempts to authenticate users by firing the same events:
Illuminate\Auth\Events\Attemptingwhen starting an attempt to authenticate.Illuminate\Auth\Events\Failedif the attempt fails.Illuminate\Auth\Events\Validatedif the attempt succeeds.
Issuing a token
When a token has been issued, it should be returned to the user. The user should then pass the token to the application as a bearer token in the Authorization header like so:
Refreshing the token in the request
The refreshed token will have all the claims from the original token and a fresh time-to-live.
Invalidating the token in the request
When the token has been invalidated, all subsequent requests with the same token will fail.
Adding claims from the user
In addition to adding custom claims through the guard configuration, it is possible to add claims to the token from the user itself.
Simply add a getClaims() method to the user model and return an array of claims:
All versions of jwt with dependencies
nesbot/carbon Version ^2.0
illuminate/http Version ^11.0
illuminate/auth Version ^11.0
firebase/php-jwt Version ^6.0
illuminate/cache Version ^11.0
illuminate/support Version ^11.0