nodejs passport authentication token
I am writing a nodejs application that I would like to use as both a web application, as well as an API provider. Once a user is authenticated, I want to assign that user a token to be used for subsequent requests. This works great with passport for the web application, as I just serialize and deserialize the user with the token in the session. However, when responding to API requests, there is no cookie to set to store the session information. Ideally, passport would look for the token both in session and the request body. Is there any way to configure passport to accomplish this?
Solution 1:
Simply use the access token on every request. Using a session is NOT needed. The following is the workflow:
POST /signin
- The username and password are posted in the client request.
- The server authenticates the user by using passport's Local Strategy. See passport-local.
- If the credentials represent a valid user, the server returns the access token generated by some generator. node-jwt-simple is a good choice.
- If the credentials are invalid, redirect to
/signin.
When the client receives the access token from the authorization server, it can then make requests to protected resources on the server. For example:
GET /api/v1/somefunction?token='abcedf'
- The client calls some server api with the token argument.
- The server authenticates the token by using passport's Bearer Strategy. See passport-http-bearer.
References
Make a secure oauth API with passport.js and express.js (node.js)
Solution 2:
As bnuhero mentions you don't need sessions (although that approach has its merits too). Here's a boiler-plate project that I'm starting for this: https://github.com/roblevintennis/passport-api-tokens
Here's an alternative and easy to follow tut (but it DOES use sessions). Might be a nice cross-reference: http://scotch.io/tutorials/javascript/easy-node-authentication-setup-and-local
And one more reference related: http://mherman.org/blog/2013/11/11/user-authentication-with-passport-dot-js/