Added middleware compatible with JWT

[BhagatHarsh]

Description

Added the middleware folder and the file auth.middleware.js containing the middleware used for auth in protected routes. checked the middleware by creating a test route.

Related Issue

This pull request is based on the issue #12.

Motivation and Context

The files changed:

server/middlewares/auth.middleware.js

contains the main logic of the middleware which extracts the Bearer token from the auth headers and verifys it using the JWT library. deals with erros as needed.

server/routes/auth.routes.js

Created a protected test route which if successfuly authenticates then sends the users information back as a JSON object.

generating a new token

request that was made using the token in the auth header

If token expires

[mirchandani-mohnish]

Is there no environment variable method to this? The private key should ideally never be exposed

[BhagatHarsh]

If you want a .env file then i can definitely make one, the reason for me doing it the easy way is that the website is still in progress most of the URL's and sensitive information is open and just for testing. so when it is finished a new PRIV_KEY will be generated and then set as the environment variable.

[mirchandani-mohnish]

Agreed but then an additional pr will have to be made for the same

How about make an env variable and additionally comment out the keys and keep

[BhagatHarsh]

@mirchandani-mohnish please review the changes.

[BhagatHarsh]

Please review the changes!