Workato/dev2

[JunyuBD]

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 14 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
-		Generic High Entropy Secret	80cc0af82fc0774c229007d11e9042063084a4b1	pre_oncall_api.go	View secret
-		Generic High Entropy Secret	9bc32390f2da21b50456993f429e235af9e5e709	pre_oncall_api/pre_oncall_api.go	View secret
-		Generic High Entropy Secret	9bc32390f2da21b50456993f429e235af9e5e709	pre_oncall_api/pre_oncall_api.go	View secret
-		Generic High Entropy Secret	b4fc17628dbdbaaaa760178ecb975601ba1cf4f4	pre_oncall_api.go	View secret
-		Generic High Entropy Secret	b4fc17628dbdbaaaa760178ecb975601ba1cf4f4	pre_oncall_api.go	View secret
-		Generic High Entropy Secret	4cda6452124b3342c3a94c74799e3ee46e77d8e1	pre_oncall_api/pre_oncall_api.go	View secret
-		Generic High Entropy Secret	fa3638e42ddd1dc1e4e334244b8883c157a825f1	pre_oncall_api.go	View secret
-		Generic High Entropy Secret	4cda6452124b3342c3a94c74799e3ee46e77d8e1	pre_oncall_api/pre_oncall_api.go	View secret
-		Generic High Entropy Secret	b53456a1ec3ee2f7cbbac44462f2f105a926d520	pre_oncall_api.go	View secret
-		Generic High Entropy Secret	4cda6452124b3342c3a94c74799e3ee46e77d8e1	pre_oncall_api/pre_oncall_api.go	View secret
-		Generic High Entropy Secret	b53456a1ec3ee2f7cbbac44462f2f105a926d520	pre_oncall_api.go	View secret
-		Generic High Entropy Secret	9bc32390f2da21b50456993f429e235af9e5e709	pre_oncall_api/pre_oncall_api.go	View secret
-		Generic High Entropy Secret	4cda6452124b3342c3a94c74799e3ee46e77d8e1	pre_oncall_api/pre_oncall_api.go	View secret
-		Generic High Entropy Secret	80cc0af82fc0774c229007d11e9042063084a4b1	pre_oncall_api.go	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 secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
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>