-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Conflict with starting DevServices if used with quarkus-oidc and Java 21 #48
Comments
Welcome to the Microcks community! 💖 Thanks and congrats 🎉 for opening your first issue here! Be sure to follow the issue template or please update it accordingly. 📢 If you're using Microcks in your organization, please add your company name to this list. 🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact. If you need to know why and how to add yourself to the list, please read the blog post "Join the Microcks Adopters list and Empower the vibrant open source Community 🙌" Hope you have a great time there! 🌟 ~~~~~~~~~ 🌟 📢 If you like Microcks, please ⭐ star ⭐ our repo to support it! 🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact. |
Hello 👋 I think this is related to the way the DevService container network is actually initialized (see quarkusio/quarkus#39899). Are you using a Quarkus version >= 3.11 ? Would you share a minimalistic Quarkus project so that I can try reproducing it? |
Hi, yes I'm using quarkus 3.12.3, see here: https://github.com/richardbischof/quarkus-microcks-oidc-reproducer I tried it with quarkus 3.10.0 also, but the error still exists.
|
Thanks for the reproducer. I started looking at it, and I succeeded in reproducing the failure. |
Hey there! Looks like I succeeded in making it start correctly by applying the same changes for database-related DevServices:
What may I check to be sure it is working as expected? Once validated, I may push my update on Quarkus upstream. |
Thank you for your quick response and your work. If I can do anything to support or double check, please let me know! :) |
Aside the DevUI checks (for both Keycloak and Microcks DevServices) is there another way to validate via your app that the fix is working? |
A fix in Quarkus has been submitted here: quarkusio/quarkus#42288 |
PR has now been merged. We have to wait for the next Quarkus release. Keeping this open in the mean time. |
Latest 3.13.1 version of Quarkus containing the bugfix resolves the reported issue |
Describe the bug
If microcks and oidc extensions are installed together, the content of two properties is overwritten
quarkus.oidc.auth-server-url=http://keycloak-j5knf:8080/realms/quarkus
keycloak.url=http://keycloak-j5knf:8080
This breaks the applications dev mode.
Expected behavior
microcks and oidc extensions can be used together.
Actual behavior
No response
How to Reproduce?
Reproducer Repository
Microcks version or git rev
0.2.6
Install method (
docker-compose
,helm chart
,operator
,docker-desktop extension
,...)quarkus ext add microcks
Additional information
No response
The text was updated successfully, but these errors were encountered: