aliirfaan/laravel-simple-jwt

Generate and verify Json Web Token (JWT) in Laravel

8.1.1 2023-06-19 07:18 UTC

This package is auto-updated.

Last update: 2024-04-30 00:50:45 UTC


README

This package allows you to generate JSON Web Tokens. You can then verify the JWT code and grant access based on its validity. You can also use the optional refresh token flow for long lived sessions. You can generate and verify JWT directly inside a controller or use the provided authentication guard.

JWT flow

  • User logs in and gets a JWT with custom claims
  • For each request consumer sends JWT
  • App verifies JWT and allow of disallow user based on validity

Refresh token flow

  • User logs in and gets a JWT with custom claims and also gets a refresh token with an expiry date
  • For each request consumer sends JWT, refresh token is extended and gets a later expiry date
  • If JWT expires, consumer sends refresh token
  • App checks if refresh token is expired
  • If refresh token is not expired, issue a JWT and extend refresh token

Features

  • Multiple JWT profiles. Each profile can have its own expiry, secret, etc...
  • Generate JWT with custom claim
  • Public claims can be included/overridden on generation
  • Verify JWT
  • Configuration for JWT expiry
  • Refresh token flow after JWT expires
  • Extend refresh token everytime the application is used so that user is not logged out
  • Blacklist user so that token is not refreshed
  • Authentication guard to authenticate users

Requirements

Installation

You can install this package on an existing Laravel project with using composer:

 $ composer require aliirfaan/laravel-simple-jwt

Register the ServiceProvider by editing config/app.php file and adding to providers array:

  aliirfaan\LaravelSimpleJwt\SimpleJwtServiceProvider::class,

Note: use the following for Laravel <5.1 versions:

 'aliirfaan\LaravelSimpleJwt\SimpleJwtServiceProvider',

Publish files with:

 $ php artisan vendor:publish --provider="aliirfaan\LaravelSimpleJwt\SimpleJwtServiceProvider"

or by using only php artisan vendor:publish and select the aliirfaan\LaravelSimpleJwt\SimpleJwtServiceProvider from the outputted list.

Apply the migrations:

 $ php artisan migrate

Configuration

This package publishes an simple-jwt.php file inside your applications's config folder which contains the settings for this package. Most of the variables are bound to environment variables, but you are free to directly edit this file, or add the configuration keys to the .env file.

The configurations are encapsulated in a profiles array with a 'default' profile available. You can add new profiles by adding a new array key.

jwt_secret | String Secret key to use to encode JWT. You can generate one using an online service (https://mkjwk.org/) or package.

'jwt_secret' => env('JWT_SECRET')

jwt_algo | String Name of supported hashing algorithm

'jwt_algo' => env('JWT_ALGO', 'HS256')

jwt_issuer | String Name of authority issuing JWT, normally your application name

'jwt_issuer' => env('JWT_ISSUER', config('app.name'))

jwt_audience | String Name of resource server that will accept the claim, normally application url

'jwt_audience' => env('JWT_AUDIENCE', config('app.url'))

jwt_does_expire | Bool (true or false) Whether the jwt expires

'jwt_does_expire' => env('JWT_DOES_EXPIRE', true)

jwt_ttl_seconds | Numeric Number of seconds after which the JWT expires if jwt_does_expire is set to true

'jwt_ttl_seconds' => env('JWT_TTL_SECONDS', 900)

jwt_leeway_seconds | Numeric When checking nbf, iat or expiration times, we want to provide some extra leeway time to account for clock skew

'jwt_leeway_seconds' => env('JWT_LEEWAY_SECONDS', 0)

jwt_refresh_should_extend | Bool (true or false) Whether we should automatically extend the JWT refresh token

'jwt_refresh_should_extend' => env('JWT_REFRESH_SHOULD_EXTEND', true)

jwt_refresh_ttl_days | Numeric Number of days to extend refresh token expiry

'jwt_refresh_ttl_days' => env('JWT_REFRESH_TTL_DAYS', 90)

Usage

New profile

<?php
// simple-jwt.php

'profiles' => [
    // default jwt settings, you can add other profiles with the same format below
    'default' => [
        'jwt_secret' => env('DEFAULT_JWT_SECRET'),
        'jwt_algo' => env('DEFAULT_JWT_ALGO', 'HS256'),
        'jwt_issuer' => env('DEFAULT_JWT_ISSUER', config('app.name')),
        'jwt_audience' => env('DEFAULT_JWT_AUDIENCE', config('app.url')),
        'jwt_does_expire' => env('DEFAULT_JWT_DOES_EXPIRE', true),
        'jwt_ttl_seconds' => env('DEFAULT_JWT_TTL_SECONDS', 900),
        'jwt_leeway_seconds' => env('DEFAULT_JWT_LEEWAY_SECONDS', 0),
        'jwt_refresh_should_extend' => env('DEFAULT_JWT_REFRESH_SHOULD_EXTEND', true),
        'jwt_refresh_ttl_days' => env('DEFAULT_JWT_REFRESH_TTL_DAYS', 90),
    ],
    'custom_profile' => [
        'jwt_secret' => env('CUSTOM_PROFILE_JWT_SECRET'),
        'jwt_algo' => env('CUSTOM_PROFILE_JWT_ALGO', 'HS256'),
        'jwt_issuer' => env('CUSTOM_PROFILE_JWT_ISSUER', config('app.name')),
        'jwt_audience' => env('CUSTOM_PROFILE_JWT_AUDIENCE', config('app.url')),
        'jwt_does_expire' => env('CUSTOM_PROFILE_JWT_DOES_EXPIRE', true),
        'jwt_ttl_seconds' => env('CUSTOM_PROFILE_JWT_TTL_SECONDS', 900),
        'jwt_leeway_seconds' => env('CUSTOM_PROFILE_JWT_LEEWAY_SECONDS', 0),
        'jwt_refresh_should_extend' => env('CUSTOM_PROFILE_JWT_REFRESH_SHOULD_EXTEND', true),
        'jwt_refresh_ttl_days' => env('CUSTOM_PROFILE_JWT_REFRESH_TTL_DAYS', 90),
    ]
]
<?php

namespace App\Http\Controllers;

use Illuminate\Http\Request;
use aliirfaan\LaravelSimpleJwt\Services\JwtHelperService; // jwt helper service

class JwtTestController extends Controller
{
     /**
     * Include our service using dependency injection
     */
    public function index(Request $request, JwtHelperService $jwtHelperService)
    {
        // jwt flow

        // payload
        $tokenPayload = array(
            'customer_id' => 1234,
        );

        // include or override claims if needed
        // useful for including project specific claims like scope, locale, nbf, etc...
        // https://www.iana.org/assignments/jwt/jwt.xhtml
        $overrideClaims = array(
            'iss' => 'custom_flow_issuer',
            'iat' => time() + 3000
        );

        // jwt token
        $profile = 'default';
        $jwt = $jwtHelperService->createJwtToken($tokenPayload, $profile, $overrideClaims);
        dd($jwt);

        // verify jwt, you will normally do this in a middleware
        $token = 'eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJMYXJhdmVsX2Jsb2ciLCJhdWQiOiJodHRwOlwvXC9sb2NhbGhvc3RcL2Jsb2ciLCJpYXQiOjE2MTIxODAyMTEsImRhdGEiOnsiY3VzdG9tZXJfaWQiOjEyMzR9LCJleHAiOjE2MTIxODExMTF9.uqFln2iQVRvaYvKDTGEG29SrT1flj9JEvFBg2zO3whM';
        $verifyJwt = $jwtHelperService->verifyJwtToken($token);
        if ($verifyJwt['errors'] == true) {

        } else {
            //get your token claims
            $tokenClaims = (array) $verifyJwt['result'];
            //dd($tokenClaims);
        }

        // refresh token flow. Using refresh flow is optional and depends on your use case
        
        $modelType = 'customer'; // your model type name you want, should be unique so that you can sent refresh tokens to multiple types of model 
        $modelId = 253; // your model id
        $refreshToken = '798798-543543-5435432543'; // the refresh token sent by consumer/client, will be null for new logins
        $deviceId = 1536-452; // your device id if you are using devic_id column

        $refreshTokenResult = processRefreshToken($modelType, $modelId, $refreshToken, $deviceId);
        dd($refreshTokenResult);
    }
}

Middleware usage

You can verify the jwt in a route middleware like below. Do not forget to register you middleware.

<?php

namespace App\Http\Middleware;

use Closure;
use aliirfaan\LaravelSimpleJwt\Services\JwtHelperService;

class SimpleJwtVerifyExample
{
    protected $jwtServiceInstance;

    public function __construct(JwtHelperService $jwtHelperService)
    {
        $this->jwtHelperService = $jwtHelperService;
    }

    /**
     * Handle an incoming request.
     *
     * @param  \Illuminate\Http\Request  $request
     * @param  \Closure  $next
     * @return mixed
     */
    public function handle($request, Closure $next)
    {
        try {

            // get token from header bearer token
            $token = $request->bearerToken();
            
            $verifyToken = $this->jwtHelperService->verifyJwtToken($token);
            if ($verifyToken['errors'] == true) {

            }

            // passed token validate, continue with request
            $tokenClaims = (array) $verifyToken['result'];
            $request->attributes->add(['token_claims' => $tokenClaims]);

        } catch (\Exception $e) {
            //
        }

        return $next($request);
    }
}

Guard usage

To use the guard, add it in your auth config

config\auth.php
    'guards' => [
        'api' => [
            'driver' => 'simple-jwt-guard',
            'provider' => 'user',
            'profile' => 'default', // the jwt profile you want to use for the provider
            'jwt_class' => null // if you have implemented your own jwt service that implements JwtServiceInterface
        ]
    ],

License

The MIT License (MIT)

Copyright (c) 2020

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.