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

hapi-auth-signi

v0.2.1

Published

hapi authentication scheme for validating signed requests

Downloads

11

Readme

hapi-auth-signi

Current Version Build Status via Travis CI Dependencies belly-button-style

hapi authentication scheme for validating signed requests. Note that this plugin is not a substitute for a full blown production auth service.

Basic Usage

'use strict';
const Hapi = require('@hapi/hapi');
const HapiAuthSignature = require('hapi-auth-signi');
const server = Hapi.server();

await server.register({
  plugin: HapiAuthSignature,
  options: {
    tenants: [
      {
        secret: 'foo',
        path: './public.pem',
        algorithm: 'sha256',
        format: 'base64',
        authData: { credentials: { username: 'peterpluck' } }
      }
    ]
  }
});

server.route([
  {
    method: 'GET',
    path: '/foo',
    config: {
      auth: 'signature',
      handler (request, h) {
        return request.auth;
      }
    }
  }
]);

Signing Requests

hapi-auth-signi expects incoming requests to include an 'Authorization' HTTP header of the following format:

Authorization: Signature signature

signature can be created using the following Node.js code:

'use strict';
const Crypto = require('crypto');
const Fs = require('fs');
const privateKey = Fs.readFileSync('./path_to_private_key');
const signer = Crypto.createSign('sha256');

signer.update('secret');
const signature = signer.sign(privateKey, 'base64');
// signature is the value to include in your request

API

hapi-auth-signi is a hapi plugin that exposes an authentication scheme named 'signature'. An authentication strategy of the same name is also created. The plugin supports the following configuration options:

tenants

An object or array of objects defining the supported clients. Each tenant adheres to the following schema.

  • secret (string) - The text that the client is expected to sign.
  • key (string or buffer) - The contents of a public key used to verify messages. Required if path is not specified. Cannot be used with path.
  • path (string) - The path to a public key file used to verify messages. Required if key is not specified. Cannot be used with key.
  • algorithm (string) - The algorithm name passed to Crypto.createVerify().
  • format (string) - The format of the signature passed to Verify.verify().
  • authData (object) - The result returned on successful authentication.

Custom Strategies

The default strategy, 'signature' uses the default settings described below. It is possible to create additional strategies by calling server.auth.strategy('your_strategy_name_here', 'signature', options) with customized options.

authorizationType

A string representing the authorization type. This is expected to be the first part of the Authorization HTTP header. Defaults to 'signature'.