Repository navigation
Replies: 5 comments 5 replies
|
Actually I was also not able to find any documentation on this. Also However this article https://blog.codecentric.de/en/2021/12/keycloak-keycloak-x/ says the you need to use the |
|
Actually the quarkus docs give some more insight on debugging |
|
@DGuhr @pedroigor Guys, I think we should add information about Quarkus remote debugging into the help and to the docs if is not there? WDYT? |
|
Sure. We haven't started writing developer guides yet, always fell down the road due to other priorities. Feel free to create an issue :) For other people landing here, to remote debug, do the following: start Keycloak using Some options:
When a build is invoked as part of the server startup (so not using --optimized and having some changes that trigger a rebuild), another JVM is spawned internally, so your debug session will be killed when the build is done and we're back in the "runtime" vm. make sure to reconnect after the |
|
Thanks, it worked. |
|
Here is the issue #13513 |
|
Throwing another way to get this with a containerized run using podman (should work for docker too): and then attach your debugger to |
|
Thanks, the |
|
For me on Keycloak 26 (quay.io/keycloak/keycloak:26.4.0) it was env:
DEBUG_PORT: '30012'
command:
- "--debug"
- "start-dev"
- "--import-realm"(no source IP needed) |
|
here is an example Maven project to debug Quarkus KC easily in an IDE. NB: Using production |
Uh oh!
There was an error while loading. Please reload this page.
Hey,
I updated my Keycloak installation from 16 (WildFly) to 18 (Quarkus). Until the update I was able to debug my custom SPI extensions with remote debugging in IntelliJ. I just had to add the DEBUG: "true" and DEBUG_PORT: "*:8787" to my docker-compose setup.
I know that the framework has changed to Quarkus and the way to remote debug has probably changed, but I can't find out how to do this with Keycloak 18.
Do you have any advices how to enable remote debugging?
Thank you!
All reactions