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

persistent-auth

v0.0.4

Published

Provide persistent authentication in your Express.JS app through cookies.

Downloads

9

Readme

Node persistent auth

Provides persistent login through cookies, following best practices described in Charles Miller's article

This library is inteded to be used together with Express.js, and optionally also with everyauth

The library should be instantiated with a store that is used to save the cookie information. The store must provide the following methods:

var persistentStore = {
	/ *
	  * Get an array of all the tokens associated with a user id. 
	  * /
	getTokens: function (userId, callback) {},
	/ *
	  *	Get a user associated with a user id.
	  * /
	getUser: function (userId, callback) {},
	/ *
	  *	Save a token with the given values. Values are, userId, salt, token and expire.
	  * /
	createToken: function (values, callback) {},
	/ *
	  * Remove the given token from the database
	  * /
	destroyToken: function (token, callback) {}
};

The callbacks given to the store follow the regular express callback style, so their signature is callback(err, arg).

Instantiation

The instantiation fo the Persistence object is shown below. The values shown are the default values, except for store, which does not have a default value.

var persistence = new Persistence({
	key: 'auth_remember' // the name of the cookie,
	store: persistentStore, // A persistent cookie store, as described above
	cookieOptions: { // The options given to res.cookie
		maxAge: 60*60*24*30*1000,
		domain: ""
	},
	separator: ';', // The symbol that should be used to separate userid and token in the cookie
	injectUser: true, // Should we inject req.user once the user is authed? 
	generateToken: function (callback) { // A function to create a random token string.
		crypto.pseudoRandomBytes(16, function (err, buff) {
			// NOTE - we do not need token values to be unique or unpredictable, as long as they are sufficiently long, thus using pseudoRandom works fine
			callback(err, buff.toString('hex'));
		});
	}
});

app.use(persistence);

Doing this will check if a cookie with the name given in key is present in the request, and if it is and session.auth is undefined the library will try to look up a matching cookie in the store, and set session.auth and req.user if it does.

To clear the cookie once a user logs out you should call persistence.clearCookie. If you are using everyauth, you can do the following:

everyauth.everymodule.handleLogout(function (req, res) {
	persistence.clearCookie(res);
	res.send(200);
});

To set a new cookie when a user logs in you call persistence.setNewToken. If you are using everyauth, this could be done in your redirectPath

app.all('/auth/response', function (req, res) {
	var respond = function () {
		res.json(200, message);
	};

	if (req.session.rememberMe === true)  {
		persistence.setNewToken(res, user, respond);
	} else {
		respond();
	}
});

As you can see from the above example, rememberMe is saved on the user session. This is because everyauth does some internal redirects, so it is not possible to pass the parameters along.