Uat

[ayanshishika]

OK

[ayanshishika]

K

[gitguardian]

⚠️ GitGuardian has uncovered 18 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
-		SonarQube Token	025c89c	pom.xml	View secret
-		SonarQube Token With Host	7e53bda	pom.xml	View secret
-		SonarQube Token With Host	180347e	pom.xml	View secret
-		SonarQube Token With Host	289453b	pom.xml	View secret
8636081	Triggered	SonarQube Token With Host	dc7d57f	pom.xml	View secret
8636081	Triggered	SonarQube Token With Host	a84efdd	pom.xml	View secret
8627629	Triggered	SonarQube Token With Host	4061677	pom.xml	View secret
8627629	Triggered	SonarQube Token With Host	c9cd640	pom.xml	View secret
9088016	Triggered	SonarQube Token With Host	25e40e8	pom.xml	View secret
9088016	Triggered	SonarQube Token With Host	805c226	pom.xml	View secret
8293853	Triggered	SonarQube Token With Host	d7ded27	pom.xml	View secret
8293853	Triggered	SonarQube Token With Host	c9bd63a	pom.xml	View secret
7644717	Triggered	SonarQube Token With Host	f532642	pom.xml	View secret
7644717	Triggered	SonarQube Token With Host	cd36874	pom.xml	View secret
8627643	Triggered	SonarQube Token With Host	c9cd640	pom.xml	View secret
8627643	Triggered	SonarQube Token With Host	dc7d57f	pom.xml	View secret
9368557	Triggered	SonarQube Token With Host	78a7e39	pom.xml	View secret
9368557	Triggered	SonarQube Token With Host	1ab633c	pom.xml	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>