Message from JavaScript discussions

January 2018

— 10 Best Practices for Writing Node.js REST APIs | RisingStack
https://blog.risingstack.com/10-best-practices-for-writing-node-js-rest-apis/

Message permanent page

— 

In order for an attacker to see session data, they would need to be able to send both the CSRF token and cookie, one of which they can't read, and the other they can't get if there are no XSS holes

— You can store a hashed CSRF token in localstorage and keep the unhashed one in the JWT.

— DiffiCULT!

— Set cookie, check cookie

— The cookie is sent automatically, so by itself is a huge CSRF risk. But, since it is HTTPOnly, scripts cant see it! The hashed localstorage CSRF token is only available to scripts on the domain, so as long as you prevent XSS, nothing would be able to compromise the tokens.

Message permanent page

— It is vastly more complex and high risk compared to server sessions and traditional CSRF token embedding

Message permanent page

— I am missing the link between backend and frontend

— HTTPOnly JWT Cookie for session token & CSRF token = no script can ever see or steal the JWT

Hashed CSRF token in localstorage = only local scripts from the origin can attempt to make requests, or XSS

Message permanent page

— With this method express will handle jwt tokens and reply to endpoint if the token is valid

— But

— Who is in charge to store the token?