Open rjrodger opened 9 years ago
This should be done by seneca-user not by seneca-auth
$ touch
I stumpled upon this article by the express-stormpath project a few days earlier: https://stormpath.com/blog/the-problem-with-api-authentication-in-express To me, but I'm not an expert in this field, the different aspects sound very reasonable. Especially the part about multiple access tokens and the key pair consisting of the user id and a random uuid.
But this issue indeed belongs to the seneca-user plugin I think.
Oh and I'm not related to express-stormpath in any way, just to say
this is more secure