testing auth types

[gauravakto]

No description provided.

[gitguardian]

⚠️ GitGuardian has uncovered 4 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
22133029	Triggered	Bearer Token	603add5	libs/utils/src/test/java/com/akto/utils/CustomAuthTestDataMother.java	View secret
22133030	Triggered	JSON Web Token	603add5	libs/utils/src/test/java/com/akto/utils/CustomAuthTestDataMother.java	View secret
22133031	Triggered	JSON Web Token	603add5	libs/utils/src/test/java/com/akto/utils/CustomAuthTestDataMother.java	View secret
22133032	Triggered	Bearer Token	603add5	libs/utils/src/test/java/com/akto/utils/CustomAuthTestDataMother.java	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.}

[devsecopsbot]

🤖 AI Security analysis: "High-risk JWT secrets are committed in test code, exposing tokens that could be abused or replayed. Remove secrets, rotate impacted credentials, and audit the repo for further leakage."

Risk Level	AI Score
🟠 HIGH	75.0/100

Top 4 security issues / 4 total (Critical: 0, High: 4, Medium: 0, Low: 0)

Title	Location	Recommendation
jwt	libs/utils/src/test/java/com/akto/utils/CustomAuthTestDataMother.java:97	jwt has detected secret for file libs/utils/src/test/java/com/akto/utils/CustomAuthTestDa…
jwt	libs/utils/src/test/java/com/akto/utils/CustomAuthTestDataMother.java:106	jwt has detected secret for file libs/utils/src/test/java/com/akto/utils/CustomAuthTestDa…
jwt	libs/utils/src/test/java/com/akto/utils/CustomAuthTestDataMother.java:148	jwt has detected secret for file libs/utils/src/test/java/com/akto/utils/CustomAuthTestDa…
jwt	libs/utils/src/test/java/com/akto/utils/CustomAuthTestDataMother.java:244	jwt has detected secret for file libs/utils/src/test/java/com/akto/utils/CustomAuthTestDa…

🔗 View Detailed Report