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

@orikami/micro-auth0

v1.0.1

Published

Micro Auth0 helper

Downloads

4

Readme

micro-auth0

Helper to get user using Auth0

Install

npm install --save @orikami/micro-auth0

Configure Auth0

By default, micro-auth0 is configured to use RS256 with the orikami.eu.auth0.com public key. It will not check for any roles by default.

You can customize and verify the configuration as follows:

  1. Create a SPA application in Auth0: https://manage.auth0.com/#/applications
  2. Settings > Advanced > OAuth > JsonWebToken Signature Algorithm: RS256
  3. Settings > Certificates > Signing Certificate contains the publickey.

If you want to customize configuration, create a auth0.js in your project:

module.exports = {
    publickey: `...` // default: orikami.eu.auth0.com
    roles: {
      key: "https://orikami-api.nl/roles",
        // allowed: ['developer'],
    },
    jwt: {
        algorithms: ["RS256"],
        // audience: "https://orikami-api.nl/v1/",
        // ignoreExpiration: false
        // issuer: "",
        // subject: "",
        // maxAge: "",
        // clockTolerance: 10
    }
}

If you define roles.allowed, micro-auth0 will check if the role in the token. Currently, this is configured using the Authorization extension of Auth0.

See https://orikami.eu8.webtask.io/adf6e2f2b84784b57522e3b19dfc9201/admins/login

Usage

const auth0 = require("@orikami/micro-auth0")(require("./auth0.js"));
const handler = require("./index");

module.exports = auth0(handler);

Known issues

publickey in auth0.js

If you change the publickey in the auth0.js file be aware that the Certificate string has no tabs or extra space in it.

Changelog

  • 1.0.0 - Change default config with ENV variables AUTH0_PUBLICKEY, AUTH0_ROLES_KEY and AUTH0_JWT_ALGORITHMS
  • 0.3.0 - Check for token query param in x-forwarded-uri
  • 0.1.0 - Refactor
  • 0.0.2 - Initial release