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

dpd-jwt

v1.0.2

Published

JWT token generator/validation Resource

Downloads

7

Readme

DPD-JWT

Simple module to create JWT tokens with Deployd

Usage

Setup

In your dpd directory type,

npm install dpd-jwt

Add a Jwt Web Token resource in the dashboard, and set the configs.

GET/POST

To get a JWT token you will need to use a POST, either internally, or externally using either REST or dpd

To get a Token on the client, use and then set a header x-token:

dpd.jwtwebtoken.get(function(error, result)) {
    // work with token that is returned
}

If you wish to use HTTP you can send a GET request to /jwtwebtoken and make sure that any user auth info is set in the headers/cookies, if you are using the User Collection that would be the sid cookie.

In the ON GET tab/event you need to validate the user and set the values object:

var val = {};
if (me) {
    // Logged in user
    val = {
        sid: 0293420kdfjsd09fs0d9fsd, // from the cookie that is set by the user collection when a user logs in
        somevalue: “anything here”,
        uid: me.id
    } 
} else {
    // Anonymous user
    val = {object that describes an anonymous user};
    // OR
    cancel(“Anonymous access denied”, 401);
}

// Set the values
setValues(val);

To get the validated and decoded result use (either on the client, or even in an event on the server):

dpd.jwtwebtoken.validate(function(error, result) {
    // work with error or result
}

To validate over HTTP make sure that the x-token header is set and make a GET request to /validate. Will return null/error or the decoded token object.

Headers

dpd-jwt uses headers to pass the JWT token around, you will need to set the header of x-token once you recieve a token using the post command.

On Post

In the ON POST event for the JwtWebToken Resource you are free to use setValues(values) to set the values/tokens you want to use in the JWTWebToken, values being an Object. You can use what ever validation you wish.

TODO

  • Add more options to config to allow for RSA key files, etc
  • Be able to send the Token with validate function with out using headers