-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
feat: add keycloak template #3109
base: next
Are you sure you want to change the base?
feat: add keycloak template #3109
Conversation
Will close this: #1819 |
Hi, thank you for your effort. I'd love to try keycloak in Coolify! Unfortunately, I had some trouble trying your proposed compose file in Coolify directly. I was sure that it was me who simply didn't understand Docker Compose and Keycloak enough. But the more I dug in, the more questions I found....
Thanks for your help |
That's how we Germans are. Just kidding. |
Have you tested another browser to see if the error also occurs there? Unfortunately, I cannot reproduce it. |
Amazing! And hello from Hamburg, Germany. I understand your choice of timezone :) You don't have to look further into the "Cookie not found" error. It was certainly due to a missing TLS certificate. The number of production-ready docker files I have written in my life is exactly zero. But since you approved my points, I feel encouraged to ask more questions, okay?
|
https://www.keycloak.org/server/all-config KC_OVERRIDE true is the default. To be honest, it was my first template for coolify. But I agree with you and can do it like that. |
@christiankolbow Does the current setup allow you to complete this simple test flow? For me, when I try to access I followed the tutorial locally. There it works. |
@TimKochDev yes sorry, you need another variable if you work with traefik. I have fixed it. |
Any updates on this? Would love to consume this service! |
Logs do appear ok though 🤷♂️:
|
Annnnnd I have no idea what fixed it but it's working now 😅 |
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
- | - | GitHub App Keys | ccbbfd8 | database/seeders/GithubAppSeeder.php | View secret |
- | - | Generic Password | e1bcae7 | templates/compose/resend.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.
This PR adds the keycloak service as a template.
( with or without postgres )