csurf VS session

To learn more about CSRF. Go here Consider using csurf

Additionally, I don't mean to offend you, but I doubt your bot will be "secure" if you don't have the appropriate knowledge and experience of secure programming practices. For example, consider this piece of code from the popular (now deprecated) csurf:

it's looking like express/csurf is archived and deprecated (as of 5 hours ago)... ref

If you use Express, I recommend using the csurf library since it's more robust and flexible compared to what I could show in this example above.

We will use a popular npm package to handle CSRF called csurf.

https://github.com/expressjs/session/issues/360 this is an issue I think that's very close to mine, no concrete solutions though..

Passport needs to be initialized as middleware as well. And it requires a session middleware for storing state and user data. The most common session middleware is express-session.

You need to pick a session store for your cookies. By default, I think express-session uses an in-memory store which means sessions are reset every time the server restarts. Redis is what I'd generally recommend for managing session stores, but setting up Redis is ANOTHER configuration update. There are a bunch of other options, too, such as using a Mongo database as a session store.

If you want to store your session data manually on Redis, check here. But in this article I will use Express session middleware which can work with Redis for user session management.

This problem can be solved by using a "session store" library such as connect-redis (see express-session's documentation for the list of session store libraries for Express.js). The idea is to keep session tokens in a dedicated database, and each time the user makes an HTTP request with their session token, the server receiving the request will consult this database to learn whether the request comes from the authenticated user or not. Performance suffers consequently, as retrieving data from a database always takes some time.