Iss58

[tung-aiden]

Sign In authentication

[gitguardian]

⚠️ GitGuardian has uncovered 9 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	Secret	Commit	Filename
5678879	Generic High Entropy Secret	fefdd4e	frontend/amplify/#current-cloud-backend/amplify-meta.json	View secret
5678879	Generic High Entropy Secret	fefdd4e	frontend/amplify/backend/amplify-meta.json	View secret
5678879	Generic High Entropy Secret	609947c	frontend/amplify/#current-cloud-backend/amplify-meta.json	View secret
5678879	Generic High Entropy Secret	609947c	frontend/amplify/backend/amplify-meta.json	View secret
5678879	Generic High Entropy Secret	609947c	frontend/src/aws-exports.js	View secret
5678879	Generic High Entropy Secret	1d98f88	frontend/src/aws-exports.js	View secret
5678879	Generic High Entropy Secret	1d98f88	frontend/src/aws-exports.js	View secret
5678879	Generic High Entropy Secret	f926bd5	frontend/src/aws-exports.js	View secret
5678879	Generic High Entropy Secret	f926bd5	frontend/src/aws-exports.js	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.

---

<sup>🦉 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.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[VincentPheng]

Missing: Login persistence

See: https://docs.amplify.aws/lib/auth/manageusers/q/platform/js/#retrieve-current-authenticated-user

Quick summary:
When a user first logs in, Amplify adds a bunch of things to the session storage and local storage. The method mentioned in the link will get those items and tell you whether or not a user is logged in. When a user is on the landing page, check if there is already a user logged in. If there is, navigate them to '/home/dashboard'. If there is no user logged in, do nothing.

[VincentPheng]

Please fix conflicts