Closed TaylorJonesTRT closed 2 years ago
Currently debating between using a cookie or JWT to store the user session. If the backend and frontend are hosted on separate services than a cross site cookie would be best in my opinion but I am also up for debate on that.
If we host the site on one server which is the most likely case then we can just use a JWT to store an encrypted secret that can only be decrypted on the backend.
User auth will be handled with Passport no matter the choice.
Going to move forward with using user authentication after all. After debating on whether to host this project or not I have decided to. With that I will need to allow people to register and log in.
I will be using oauth with Google to allow a simpler sign in but also will allow the use of usernames and password combinations.
For user authentication I will need to rework my models/schemas to support a user system rather than a local install of all dependencies. I will go further into this in my next reply.
Description User authentication will need to be added to the project. Instead of forcing anyone that wants to use this web app to have to figure out how to install a bunch of dependencies and dev environments we can add user auth and just host the project ourselves while still allowing anyone who wants to just run it locally on their own machine the option for that as well.