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

cryotokens

v1.0.1

Published

Freeze JSON Web Tokens until expiry

Downloads

1

Readme

Cryotokens

Simple NodeJS module to keep and check against a list of JSON Web Tokens (JWT) until their expiration, allowing for a "logout" and "logout from all other devices" functionality to auth systems that use stateless tokens.

⚠️ Warning! ⚠️

This is a work in progress and is NOT production ready yet.

Prerequisites

A running Redis server is needed, unless running Test mode (in memory) as specified in the Configuration section below.

If the "logout from all other devices" functionality (freezeSub method) is used, the JWT needs to have a sub property in their payload, which refers to the subscriber (usually the id of the user associated with that token). This is required to filter all tokens from the same user.

Installation

$ npm install --save cryotokens

Usage

Initialization (a secret is required)

The modules needs to be initialized (ran as a function) and has only one required parameter: the secret used to verify the JWT.

const ct = require('cryotokens')('somesecret');

Ideally this isn't hardcoded on your code but instead grabbed as a environment variable:

const secret = process.env.JWT_SECRET;
const ct = require('cryotokens')(secret);

Freeze token (Logout)

ct.freeze(token);

Freeze subscriber (Logout from all devices)

ct.freezeSub(token);

Check token

Returns the decoded token if it's not on the list and valid. Otherwise it throws an error if the token is frozen, expired or invalid.

ct.check(token)
  .then(decoded => console.log('Decoded token: ', decoded))
  .catch(error => console.log('An error ocurred', error));

or inside try/catch blocks:

try {
  const decoded = ct.check(token);
  console.log('Decoded token: ', decoded));
} catch(error) {
  console.log('An error ocurred', error));
}

Configuration

Cryotokens uses this redis client and thus accepts its options listed here. It uses the default host (127.0.0.1) and port (6379) for the Redis server. The only option this library sets is prefix, which adds cryotokens: to beginning of the database keys.

Those options can be overriden by passing a second parameter to the imported module:

const config = {host: 'somehost.com', port: 6378};
const ct = require('cryotokens')('somesecret', config);

Test mode (in memory)

To store tokens in memory (no Redis install needed) just pass {test: true} as second parameter.

const ct = require('cryotokens')('somesecret', {test: true});

Tests

Tests use jest, redis-mock and sinon (for simulating expiry). To run them:

$ npm test

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

Roadmap

  • [ ] Better error handling
  • [ ] Express middleware that validates token from request header and handles auth
  • [ ] Fail safely (if Redis is down)

License

MIT