Release #16
Merged
Release #16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Eoepca 910 um keycloak develop an identity api based on keycloak api (#9) * feat: keycloak_client methods added for identity_api * feat: added scopes crud (for future?) and fixes on permissions and policies cruds * Merge (#10) * Update docker compose * Fix keycloak client constructor * Update README.md * Update docker compose * Add nginx config * Change nginx * Add realm admin role * Remove auth keycloak client (#11) * Add dummy service demo * Add dummy-service nginx * Update demos * Update nginx configs * Update gatekeeper config * feat: added register_general_policy function * fix: small fix in register_general_policy * fix: one more fix * feat: added delete permissions * feat: added create client function * Add gatekeeper cookie name * Improve create client script * feat: added inputs to script but not working yet * Update create-client.sh * Update create-client.sh * Update create-client.sh * Update create-client.sh * Update create-client.sh * Update create-client.sh * Update create-client.sh * Fix issues * Improve create client script * Fix issue * Fix keycloak client * Cleanup and reformat --------- Co-authored-by: flaviorosadme <[email protected]> Co-authored-by: flaviorosadme <[email protected]>
|
| GitGuardian id | Secret | Commit | Filename | |
|---|---|---|---|---|
| 6968476 | Generic High Entropy Secret | f78d1f0 | helm/charts/identity-oauth2-proxy/values.yaml | View secret |
| 6968476 | Generic High Entropy Secret | f78d1f0 | helm/charts/identity-oauth2-proxy/values.yaml | View secret |
| 6968476 | Generic High Entropy Secret | 675118e | helm/charts/identity-oauth2-proxy/values.yaml | View secret |
| 6968476 | Generic High Entropy Secret | 675118e | helm/charts/identity-oauth2-proxy/values.yaml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- 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.
Our GitHub checks need improvements? Share your feedbacks!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.