Forgot and Reset Password Implemented

[niteshtiwari52]

@adil-techcode First of all, I am so sorry for commit and pushing the code late.

Issue No : #34

I have implemented the forgot and reset password using the OTP Verification.

Setup or Environment Variable required: PORT : optional and anything DATABASE_URL : database connection url JWT_SECRET : A secret key to generate token securely and this can be anything of your choice. CLIENT_URL: Our frontend base url where our frontend application hosted.

SMTP_SERVICES: Your mailing service (e.g., "gmail"). SMTP_MAIL: Your email address from which the emails will be sent. SMTP_PASSWORD: The application-specific password for your email account. SMTP_HOST: The SMTP host address for your email service (e.g., "smtp.gmail.com"). SMTP_PORT: The port number for your SMTP service (e.g., 465 for Gmail).

I am also attaching the postman documentation for sample data. Postman Documentation: https://documenter.getpostman.com/view/23029976/2sA3QqhYdF

If Any further disscussion or help required, please feel free to contact.

[vercel[bot]]

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

Name	Status	Preview	Comments	Updated (UTC)
shopy-frontend	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 30, 2024 11:39am

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 2 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 | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [-](https://dashboard.gitguardian.com/workspace/430970/incidents/secrets) | | Generic Password | efe82e355e3db71e566d35abd3bfe6dfd24b33aa | server/.env | [View secret](https://github.com/mohitparmar1/Shopy/commit/efe82e355e3db71e566d35abd3bfe6dfd24b33aa#diff-851502e39b7ba2dbf4da21e578181c158ff8917752cefcae5996bd989915e25dR8) | | [-](https://dashboard.gitguardian.com/workspace/430970/incidents/secrets) | | Generic Password | 4dd1edcd5368d6f7becc12107defeb8a3c1757b0 | server/.env | [View secret](https://github.com/mohitparmar1/Shopy/commit/4dd1edcd5368d6f7becc12107defeb8a3c1757b0#diff-851502e39b7ba2dbf4da21e578181c158ff8917752cefcae5996bd989915e25dL8) |

🛠 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](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate these secrets](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/generics/generic_password#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 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](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) 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.}

[mohitparmar1]

resolve conflicts!

[niteshtiwari52]

conflicts has been resolved now. you can close now this issues if every thing is working fine. If any help or any disscussion needed for this pull request, I will be avaialable