Feat: signin a user with email and password

[Ndevu12]

Description

This PR introduces a new feature that allows users to sign in using their email and password.
Also it Implement error handling for cases where the user tries to sign in with an invalid email or password.

Changes

• Added a new endpoint POST /user/signin that handles user sign-in.
• Implemented a function to validate the user's email and password.
• If the validation is successful, the server responds with a cookie containing the user's access token.

Test Plan

• Added unit tests for the POST /user/signin endpoint in signin.test.ts.
• The tests cover the case where a user signs in with a valid email and password.
• After all tests, the database connection is closed to prevent any hanging test cases.

[gitguardian]

⚠️ GitGuardian has uncovered 8 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
10624400	Triggered	Generic Password	d46968c	src/test/signin.test.ts	View secret
10624400	Triggered	Generic Password	d46968c	src/test/signin.test.ts	View secret
10624401	Triggered	Generic Password	d46968c	src/test/signin.test.ts	View secret
10624401	Triggered	Generic Password	d46968c	src/test/signin.test.ts	View secret
10624402	Triggered	Generic Password	d46968c	src/test/signin.test.ts	View secret
10624402	Triggered	Generic Password	d46968c	src/test/signin.test.ts	View secret
10624403	Triggered	Generic Password	d46968c	src/test/signin.test.ts	View secret
10624403	Triggered	Generic Password	d46968c	src/test/signin.test.ts	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[faid-terence]

@Ndevu12 !!What's the progres ?

[Ndevu12]

Sorry I forgot to send JWT_SECRET_KEY. But you can find it on slack now.

…

On Thu, May 2, 2024 at 11:44 PM Terence Faid JABO ***@***.***> wrote: @Ndevu12 <https://github.com/Ndevu12> !!What's the progres ? — Reply to this email directly, view it on GitHub <#53 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBQ2IHIN2I4XHKYTWUHA6ODZAKXT3AVCNFSM6AAAAABHD3BXKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJRG44DENJXG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[faid-terence]

@Ndevu12 !
please squash the commit messages!!

[Ndevu12]

@faid-terence
That is what Am going to be working on

[faid-terence]

We can't merge this PR !, Please squash commit messages !

[Ndevu12]

Now we have one commit

[coveralls]

Pull Request Test Coverage Report for Build 8935890322

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 73.099%

---

Totals
Change from base Build 8919969005:	0.0%
Covered Lines:	109
Relevant Lines:	136

---

💛 - Coveralls