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

jwks-terminal

v0.0.8

Published

A collection of utilities when working with JWKS (JSON Web Key Store).

Downloads

25

Readme

JWKS Terminal

JWKS (JSON Web Key Store) terminal is a collection of utilities for when working with JWKS backend store.

Usage

JWKS Terminal can be used in the following manner:


function Db = function (options) {
  ... // use npm package secrets-manager-pg-cache for connection pooling
};

Db.prototype.query = function (text, params) {
  ...
};

Db.prototype.execute = function (text, params) {
  ...
};

Db.prototype.client = function () {
  ...
};

const jwt = require('jsonwebtoken');
const crypto = require('crypto');
const uuid = require('uuid/v4');
const ber = require('asn1').Ber;
const minimatch = require('minimatch');
const passport = require('passport');
const express = require('express');

const SecretOrKeyProviderFactory = require('jwks-terminal').SecretOrKeyProviderFactor;
const JwtStrategyFactory = require('jwks-terminal').JwtStrategyFactory;
const JwtAuthorization = require('jwks-terminal').JwtAuthorization;
const Jwk = require('jwks-terminal').Jwk;
const JwtStrategy = require('passport-jwt').Strategy;
const ExtractJwt = require('passport-jwt').ExtractJwt;

const db = new Db({ ... });

const jwk = new Jwk({
  db: db,
  jwt: jwt,
  crypto: crypto,
  uuid: uuid,
  ber: ber,
  ...
});

const secretOrKeyProviderFactory = new SecretOrKeyProviderFactory({
  jwt: jwt,
  jwk: jwk
});

const jwtStrategyFactory = new JwtStrategyFactory({
  ExtractJwt: ExtractJwt,
  JwtStrategy: JwtStrategy,
  issuer: ...,
  ...
});

const secretOfKeyProvider = secretOrKeyProviderFactory.get();
const jwtStrategy = jwtStrategyFactory.get();
const jwtAuthorization = new JwtAuthorization({
  minimatch: minimatch
});

passport.use(jwtAuthorization);

const app = express();

app.use(passport.initialize());

app.get('/',
    passport.authenticate('jwt', { session: false }),
    jwtAuthorization.apply(['jwks:ListJwk']),
    (req, res, next) => {
        jwk.list(req.user.sub)
            .then(data => {
                return res.status(200).send(data);
            })
            .catch(err => {
                return next(err);
            });
    });

app.listen(...);

Testing

Both integration and unit tests can be run via separate commands, namely:

  1. npm test
  2. npm run integration

In order for integration tests to be run, a postgres instance should be running locally. This can be done via docker using the following command:

docker run --name postgres -e POSTGRES_USER=test -e POSTGRES_DB=jwks -e POSTGRES_PASSWORD=test -p 5432:5432 -d postgres