schmidt-authentication-project

[ ] Login form with 2 fields - username and password
[ ] Users only have to log in once (i.e. implement a cookie-based session on login)
[ ] Username is visible on each page of the site after logging in
[ ] Any user-submitted content should be labelled with the authors username
[ ] There should be protected routes and unprotected routes that depend on the user having a cookie or not (or what level of access they have).
[ ] Website content should be stored in a database
[ ] Include thorough tests on the back-end, testing pure functions and testing routes using Supertest. If you make external API calls, use Nock to mock the response for your tests.
[ ] Test front-end logic, we don't expect tests on the DOM. authentication with cookies and jwt

Day 1

Hannah and Sak working on getting the post request working so that we can add new users to our user table in our database.
Mike and Charmaine working on cookies and log-in page
Hannah and Charmaine work on hashing passwords

Server-side validation getting the data posted to a route that will be able to monitor and handle.
hashing not using bcrypt.compare which means we were having problem with password confirmation because we had different hashes.
CSS on the auth page doesn't work
no database testing
no message for password entry
module exports