-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Access control #38
Access control #38
Conversation
|
Secret | Commit | Filename | Detected At | |
---|---|---|---|---|
Generic High Entropy Secret | acc7daf | documentation/Keycloak/keycloak-realm.json | 13:42 December 23rd, 2021 | View secret |
Generic High Entropy Secret | acc7daf | documentation/Keycloak/keycloak-realm.json | 13:42 December 23rd, 2021 | View secret |
Generic Password | acc7daf | documentation/Keycloak/keycloak-realm.json | 13:42 December 23rd, 2021 | 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 is an automated secrets detection service.We help developers and security teams secure the modern software development process.
Our GitHub checks need improvements? Share your feedbacks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Made some language suggestions
@GuentherJulian please check the credentials and please redo a clean PR. There are private keys here as part of the PR. |
|
||
You can access Keycloak by navigating to http://localhost:8180/auth/ in your browser. Open the Administration console and log in with the default username "admin" and password "admin". | ||
|
||
The first step is to create a new realm. A realm in Keycloak is used to manage a set of users with their credentials, groups and roles. Click on "Add realm" and then select the `keycloak-realm.json` file from the documentation/Keycloak folder of this repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe mention that you need to hover over the "Master" dropdown-menu to expose the "Add realm" button. It took me a minute :)
</dependency> | ||
---- | ||
|
||
The extensions is already included in the dependencies. To enable it, set `quarkus.smallrye-jwt.enabled=true` in the `application.properties` file. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The extension is already included in the dependencies.
Closes #27