schmidt-authentication-project

Start instructions

• git clone
• get the config.env (in gitter)
• npm i
• npm run dev
• view on port 5000

Requirements

• 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

Planning and setup

Day 1

• Hannah and Charmaine worked together to create and populate database
• Sack and Mike set up signup page with client-side validation
• we had trouble not exporting roots in handler, not requiring the JS files.

Day 2

• 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

Challenges and Lessons

• 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

Victories

• Leaving early
• Client-side validation
• Everyone knows what the code is doing/ not doing
• Working together well
• Got POST request working
• Got Cookies working (kinda)