Secure client stored session management middleware. The module provides session management functionality for stateless server applications. This is achieved by encrypting the session data and storing/reading chunks of it ( depending on data size ) in an appropriate number of cookies.

Installation

npm install stateless-session -save

Usage

It is realy simple to use just type :

var session = require ( ' stateless-session ' ) ; app . use ( session . middleware ( ) ) ;

and you are good to go. This will setup the session for the current request.

You can access the session object and assign data to it later in your application by using the req.session object.

var session = require ( ' stateless-session ' ) ; app . use ( session . middleware ( ) ) ; app . get ( ' /login ' , function ( req , res ) { req . session . start ( ) ; req . session . username = " skpapam " ; req . session . email = " contact@skevosp.me " ; res . send ( " You are now logged in and your session id is " + req . session . getId ( ) ) ; } ) ; app . get ( ' /hidden ' , function ( req , res ) { if ( req . session . hasStarted ( ) ) { res . send ( " This is your private page " + req . session . username ) } else { res . send ( " This page is private. You have to login first " ) } } ) ; app . get ( ' /logout ' , function ( req , res ) { req . session . stop ( ) ; res . send ( " You are now logged out. Your last activity was at : " + req . session . lastActivity ( ) ) ; } ) ;

As you can see in the above example session tracking does not start by default in order to provide authorization functionality to applications.

When the user visits the /login we call req.session.start() that starts the session and assigns a session id then our session data will be encrypted and passed through a single cookie in our case ( small data size ) to our client. If we don t do that there will be no cookies returned to client thus all session variables will be lost.

When the user visits our /hidden page we check if the session has started and return the appropriate message.

When the user visits the /logout page we stop the session tracking which will cause our cookies to expire thus our data to delete.

You can ignore this feature and provide guest-like sessions by setting the autostart option to true ( default is false )

var session = require ( ' stateless-session ' ) ; app . use ( session . middleware ( { ' autostart ' : true } ) ) ; app . get ( ' /addName ' , function ( req , res ) { req . session . name = " Skevos " ; res . send ( " Name added " ) ; } ) ; app . get ( ' /getName ' , function ( req , res ) { res . send ( " The name is : " + req . session . name ) ; } ) ;

The options that you can pass to the middleware are the following :

key {String} Overrides the default key for encryption. See more i-encrypt

Overrides the default key for encryption. See more i-encrypt debug {Boolean} Debug mode switcher for encryption. See more i-encrypt

Debug mode switcher for encryption. See more i-encrypt autostart {Boolean} Switch from authorized sessions ( false ) to guest ones ( true ) default value is false

Switch from authorized sessions ( false ) to guest ones ( true ) default value is false prefix {String} A cookie name prefix. Default value is 's_d_'

A cookie name prefix. Default value is c_options {Object} Cookie related options for more see cookie. By default path option is set to '/'

Limitations

Even though this module manages to overcome the 4KB cookie size limitation by distributing the data to multiple cookies based on its size there is still the overall size limitation per domain which depends on each browser. Most modern browsers will support up to 80KB of data.

Before setting your application's session to handle a big load of data please read this.

License

MIT

Copyright (c) 2016 Skevos Papamichail <contact@skevosp.me> (www.skevosp.me)