Frontend release/1.0

[Mburu-Elvis]

No description provided.

[gitguardian]

⚠️ GitGuardian has uncovered 13 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
9399751	Triggered	Generic Password	1ab9ea5	backend/src/main/resources/application.properties	View secret
9399751	Triggered	Generic Password	6c8bacf	mobilleWallet/src/main/resources/application.properties	View secret
12601973	Triggered	Bearer Token	1d719e3	mobilleWallet/src/main/java/natujenge/com/mobilleWallet/service/AccountService.java	View secret
12601973	Triggered	Bearer Token	398d5cc	mobilleWallet/src/main/java/natujenge/com/mobilleWallet/service/AccountService.java	View secret
12601973	Triggered	Bearer Token	4d98a9f	mobilleWallet/src/main/java/natujenge/com/mobilleWallet/helper/Messaging.java	View secret
12601973	Triggered	Bearer Token	cc586e7	mobilleWallet/src/main/java/natujenge/com/mobilleWallet/helper/Messaging.java	View secret
12601973	Triggered	Bearer Token	94fe075	mobilleWallet/src/main/java/natujenge/com/mobilleWallet/helper/Messaging.java	View secret
12601973	Triggered	Bearer Token	519d8f8	mobilleWallet/src/main/java/natujenge/com/mobilleWallet/helper/Messaging.java	View secret
12601973	Triggered	Bearer Token	b4979ae	mobilleWallet/src/main/java/natujenge/com/mobilleWallet/helper/Messaging.java	View secret
12601973	Triggered	Bearer Token	dc0c3dc	mobilleWallet/src/main/java/natujenge/com/mobilleWallet/helper/Messaging.java	View secret
12601973	Triggered	Bearer Token	93bf968	mobilleWallet/src/main/java/natujenge/com/mobilleWallet/helper/Messaging.java	View secret
13202014	Triggered	Username Password	398d5cc	mobilleWallet/src/main/resources/application.properties	View secret
13202014	Triggered	Username Password	bc06717	mobilleWallet/src/main/resources/application.properties	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.}