Skip to content

Dev - #2

Open
cuong02n wants to merge 70 commits into
masterfrom
dev
Open

Dev#2
cuong02n wants to merge 70 commits into
masterfrom
dev

Conversation

@cuong02n

Copy link
Copy Markdown
Owner

No description provided.

cuong02n and others added 30 commits April 29, 2024 13:38
Make CourseId as Primary Key for Entity: Course
@gitguardian

gitguardian Bot commented Jul 11, 2024

Copy link
Copy Markdown

⚠️ GitGuardian has uncovered 12 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
10568728 Triggered Generic Password 3f680c6 src/main/resources/application.properties View secret
10568728 Triggered Generic Password fa47678 src/main/resources/application.properties View secret
10568728 Triggered Generic Password 847f42f src/main/resources/application.properties View secret
10568728 Triggered Generic Password 128eb54 target/classes/application.properties View secret
10568728 Triggered Generic Password 128eb54 src/main/resources/application.properties View secret
10568728 Triggered Generic Password d615e6a src/main/resources/application.properties View secret
13018476 Triggered MySQL Credentials d615e6a target/classes/application.properties View secret
13018476 Triggered MySQL Credentials c491afa target/classes/application.properties View secret
13018477 Triggered MySQL Credentials d615e6a src/main/resources/application.properties View secret
13018477 Triggered MySQL Credentials c491afa src/main/resources/application.properties View secret
13045647 Triggered MySQL Credentials c491afa src/main/resources/application.properties View secret
13045648 Triggered MySQL Credentials c491afa target/classes/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


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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants