Pushing you Onward with your knowledge of Authentication.

DISCLAIMER Authentication is a subject that many people spend a large amount time throughout their careers obtaining knowledge over. This is not something we expect you to have a mastery over, rather, we're preparing you to be able have an intelligent conversation about the subject.

The objective of this challenge is to get you used to answering a few questions about Authentication.
We also have some more reps for you to help hammer in the knowledge you've thus far learned.
Answers to your written questions will be recorded in Answers.md
This is to be worked on alone but you can use outside resources. You can reference any old code you may have, and the React Documentation, however, please refrain from copying and pasting any of your answers. Try and understand the question and put your responses in your own words. Be as thorough as possible when explaining something.
Just a friendly Reminder Don't fret or get anxious about this, this is a no-pressure assessment that is only going to help guide you here in the near future. This is NOT a pass/fail situation.

Start by forking and cloning this repository.

What we have here is a wise-guy application. Dad jokes are all the rage these days.
Our main problem with the application now is that we are trying to receive some mad dad jokes that are being requested from an external api, but we are locked out.
Trust me, we all need these dad jokes in our lives.
In order to be able to access our Killer Jokes you'll need to implement a User Authentication System that uses bcrypt and JWT.

cd into the root of the project and run npm install.
Once you have your node_modules go ahead and start your mongod server * I recommend using the mongod --dbpath data flag.
Run nodemon app.js to start your node server.
TEST this project using POSTMAN. Once you finish the project, you'll be tasked to set up cors properly for use with a client.

The required fields are username (must be unique and required) and password.

{
  "username": "Tony@stark.com",
  "password": "pepperpots"
}

Start in api/utils/middlewares.js.
Follow the steps provided in the encryptPW function. Once done there, head back here for further instructions.
Check out api/controllers/user.js. There are some things to implement there.
Once you have your controller implemented, head over to your api/routes/routes.js file and notice we have a controller missing. Go ahead and pass in this controller.
TEST your /api/user POST to ensure you can create a user with an encrypted password.

This step will be real fun.
Head over to your comparePW function in api/utils/middlwares.js and follow the instructions for the that piece of login middleware.
Once you have compared passwords with bcrypt, you'll need to **ENSURE THAT** you have set the req.username as the user's username. Without it, your login controller won't know what to do and you'll receive this error:

 error: 'no username check your comparePW middleware'

Grab your Token sent back to you in JWT format from /login.
Send a GET request up to /api/jokes with the appropriate
Without the appropriate request you'll get an error that looks like this from the jwt package

{
    "name": "JsonWebTokenError",
    "message": "invalid signature"
}

In order to play around with a client server app, you'll need to set up your cors inside of server.js properly.
Using React and Redux and React Router, create a Sign Up, Sign In and Jokes page.
Once you have the functionality down, you'll be able to style it up a bit and play around with the jokes etc.