npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

jwt-policy

v0.7.0

Published

JSON Web Token middleware friendly with Express and Sails.js

Downloads

3

Readme

jwt-policy

npm version

JSON Web Token middleware friendly with Express and Sails.js

Validates token from HTTP request header authorization and sets req.user, token is expected to be found at Authorization: Bearer <token>.

This module verifies tokens generated with node-jsonwebtoken

Install

$ npm install jwt-policy --save

Usage

jwtPolicy(options, [callback])

options :

  • secret : is a string containing the secret for decoding token.
  • extractToken : function to extract token instead of default (HTTP Authorization Header).
  • attachTo : allows the user to override the default path where the decoded token will be attached to, default is user.

Note: You can pass all available options for jwt.verify such as audience, issuer, etc.

Specify callback if you wish to do something with req.user or check for possible errors, if callback is not supplied then default behavior will take effect.

For default, jwt-policy extracts token using extractor-token (HTTP Authorization Header) but in case you are passing the token by any other method you can use extractToken option.

Usage in Sails.js

Default behavior

// Will return 401 HTTP status code if any errors occurred.
// policies/jwtAuth.js
module.exports = require('jwt-policy')({ secret: 'my_secret_key' });

Override default behavior

// policies/jwtAuth.js
module.exports = require('jwt-policy')({
  secret: 'my_secret_key'
}, function(err, req, res, next) {
  if (!err) {
    // user can be found at 'req.user'

    return next();
  }

  return res.status(401).json(err);
});

Override the way the token is extracted using extractToken option.

// policies/jwtAuth.js
module.exports = require('jwt-policy')({
  secret: 'my_secret_key',
  extractToken: function(req) {
    return req.param('token');
  }
});

Usage in Express

Default behavior

const jwtPolicy = require('jwt-policy');

app.get('/', jwtPolicy({ secret: 'my_secret_key' }), function(req, res) {
  res.send(req.user);
});

Override default behavior

const jwtPolicy = require('jwt-policy');

app.use(jwtPolicy({ secret: 'my_secret_key' }, function(err, req, res, next) {
  if (!err) {
    return res.next();
  }

  return res.status(401).json(err);
}));

app.get('/', function(req, res) {
  res.send(req.user);
});

Override the way the token is extracted using extractToken option.

app.use(jwtPolicy({
  secret: 'my_secret_key',
  extractToken: function(req) {
    return req.query.token;
  }
}));

Attach to

attachTo option usage example:

const jwtPolicy = require('jwt-policy');

app.use(jwtPolicy({
  secret: 'my_secret_key',
  attachTo: 'auth'
}));

app.get('/', function(req, res) {
  // decoded token can now 
  // be found at `req.auth`
  res.send(req.auth);
});

Error handling

Possible thrown errors

TokenExtractorError

| message | code | | ----------------------------------------------- |:------------------------------------:| | No Authorization header is present | E_AUTHORIZATION_REQUIRED | | Format is :: Authorization: Bearer | E_AUTHORIZATION_INVALID_FORMAT | | Authorization token was not found | E_AUTHORIZATION_TOKEN_NOT_FOUND |

JWTError

| message | code | | ----------------------------------------------- |:------------------------------------:| | JSON Web Token provided has expired | E_TOKEN_EXPIRED | | Invalid JSON Web Token provided | E_TOKEN_INVALID |

Suppose E_TOKEN_EXPIRED error was thrown

app.use(jwtPolicy({ secret: 'my_secret_key' }, function(err, req, res, next) {
  if (err) {
    console.log(err.toJSON());
    /*
      {
        status: 401,
        message: 'JSON Web Token provided has expired',
        code: 'E_TOKEN_EXPIRED'
      }
    */

    console.log(err.toString());
    /*
      [JWTError (E_TOKEN_EXPIRED) JSON Web Token provided has expired]
    */

    console.trace(err);
    /*
      prints Error Stack since err instanceof Error
    */
  }
}));

Test

$ npm test