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

eyeos-auth

v1.0.471

Published

Library to validate user cards dispached by login

Downloads

4

Readme

Eyeos-auth Library

Overview

The eyeos-auth library is intended to generate authorization cards signed by itself and validate them in different backend services.

How to use it

The cards follow the format:

{
    "card": '{"username": "an-user", "domain":"the user domain", "expiration": epoc-timestamp, "permissions": ["",""]}',
    "signature": "signature-generated-by-server",
    "permissions": ["permission1", ...],
    "expiration": epoch_ts_when_card_expires_in_seconds,
    "renewCardDelay": seconds_from_card_creation_to_renew_card
}

A card contains a username, represented by a string (can be a username, a email, whatever its in ldap)., A timestamp with the date limit when this card is no longer trusted. An array of permission nodes. Each permission is a string with a given permission.

Development mode

If you are using eyeos-auth in a development environment and want to bypass real validation, just set an environment variable:

export EYEOS_DEVELOPMENT_MODE=true && node my-amazing-service.js

For component test only

You can get a card (with or without permissions) in order to execute requests that needs credentials. It is useful if the services you test do not interact with the authentication service directly but you need valid card and signature.

var eyeosAuth = new EyeosAuth();
var credentitals = eyeosAuth.getFakeAuth('fakeUser', [ 'my.permission' ]);
// now you can access to credentials.card and credentials.signature

Quick help

  • Install modules
	$ npm install
  • Check tests
    $ grunt test