samedi 4 avril 2015

Should I consolidate session management using Sails.js and Stormpath?

I'm investigating using Stormpath for our user Management.


I currently have a Sails.js application which uses Node.js / Express.js. Currently, session management is handled by the default Sails.js framework, which relies heavily on Express' session middleware.


Sessions are stored in a shared Redis database on production so that we can keep our multiple API servers stateless.


My question is will the two session management systems conflict and/or cause bugs? Do they have to be consolidated or can we safely keep them separate? if they have to be combined, how do you configure the middleware?


As a note we won't be storing much user data on Stormpath, we'll only be using them as a auth/token provider.


Thanks for the help!


Aucun commentaire:

Enregistrer un commentaire