Feat: basic middleware structure to support authenticating requests

[JacobWithACapitalJ]

No description provided.

[vercel]

Someone is attempting to deploy a commit to a Personal Account owned by @Jomy10 on Vercel.

@Jomy10 first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
polls	✅ Ready (Inspect)	Visit Preview	May 19, 2022 at 10:33PM (UTC)

[Jomy10]

Awesome! I'll test this out tomorrow. Only problem right now will be deployment to Vercel, as Vercel looks at the api directory for serverless functions. So we'll have to figure out how to get this working on Vercel.

[Jomy10]

Alright. I've reviewed the pull request, I'll merge it after this question:

How do we generate the X-Poll-Token on the client?

[JacobWithACapitalJ]

Alright. I've reviewed the pull request, I'll merge it after this question:

How do we generate the X-Poll-Token on the client?

Sorry, been a bit tied up with work recently! I'll implement the token generation on the weekend.
My idea of the auth flow is:
user inputs poll ID -> token is generated with a random ID and returned from /info endpoint -> user votes -> token is validated before writing vote to DB (with the tokens ID) -> user tries to vote again -> vote endpoint looksup votes with that token ID and rejects if documents are returned

[Jomy10]

That sounds good to me!

Let me know if you need anything.

P.S. Don't worry, there's no hurry!