implement login funcationality

[MaheshBabu151mb]

Description

Please include a summary of the changes and the related issue.

Fixes # (issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

• Test A
• Test B

Test Configuration:

• Hardware:
• Toolchain:
• Other:

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works

Screenshots (if applicable)

If applicable, add screenshots to help explain your changes.

Additional Information

Any additional info that might be helpful in reviewing pull request.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
automarket	❌ Failed (Inspect)			Sep 27, 2024 11:29am
automarket-backend	❌ Failed (Inspect)			Sep 27, 2024 11:29am
automarket-s42l	❌ Failed (Inspect)			Sep 27, 2024 11:29am

[github-actions]

Welcome to Our repository.🎊 Thank you so much for taking the time to point this out.

[gitguardian]

⚠️ GitGuardian has uncovered 3 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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
10921764	Triggered	RapidAPI Key	97133ba	frontend-app/fastapi-rest-apis/actions/scripts/textSummarizer.py	View secret
11136913	Triggered	PostgreSQL Credentials	97133ba	frontend-app/fastapi-rest-apis/db/index.py	View secret
-	-	Generic High Entropy Secret	97133ba	frontend-app/fastapi-rest-apis/actions/scripts/imageGenerationAI.py	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.}