Home/ Questions/Q 8298771
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-08T15:54:20+00:00

I have a web tool developed, which uses node.js and socket.io. it’s a one

  • 0

I have a web tool developed, which uses node.js and socket.io. it’s a one page website and uses node.js for getting data from social media website and display on the same page. I would like to add a site specific login system for the website but don’t want to use ‘Express‘ or ‘Passport‘ as it adds lots of overload to the website while it is not needed.

I am newbie with node.js and would like to know if I need to have a login system made with node.js to maintain session of the logged in user?

Note: I need to maintain session to log user data such as login time, search query and may be heatmap.

Thanks in advance. If needed I can explain specific part of the question in detail.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Using something like Express or Passport (or at least some of connect’s middleware) will definitely be easier in the long run (if your app grows), but if you want to go the ‘manual’ route, here are some starting points:

    1. Cookie Parser: You won’t want to send the auth details with every request as a parameter, so you’ll want to put the session details in a cookie. You can set cookies manually using headers, or with a node module that wraps the API neatly.

    2. Session Storage: You can put all the “login time, queries and heatmap data” in cookies, but it would be neater to just send a session id in the cookie in each request and save the other data server-side in a database. Options are mongoose, redis, etc.

    Since reading the source is very educational, go read connect’s cookieParser and cookieSession. It’s not a lot of code and the API docs include the actual source, so it’s very easy to learn from. Enjoy! 🙂

    • 0