Keycloak DevService does not start for Keycloak Admin Client

[sberyozkin]

Describe the bug

I noticed the other day when investigating a failure in the now merged Peter's PR, that if the forced quarkus-oidc-deployment is removed in the extensions/keycloak-admin-reasteasy-client/deployment tests, then Keycloak Dev Service does not start.

May be I got it wrong, sorry if it proves the case.

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[quarkus-bot]

/cc @geoand (devservices), @pedroigor (keycloak), @stuartwdouglas (devservices)

[sberyozkin]

@gsmet It's a bug, this is supposed to work already

[michalvavrik]

It doesn't start because you have set the server URL:

• quarkus/extensions/keycloak-admin-resteasy-client/deployment/src/test/resources/app-dev-mode-config.properties

  Line 5 in e4cab19

  quarkus.keycloak.admin-client.server-url=http://localhost:${quarkus.keycloak.devservices.port}

• quarkus/extensions/keycloak-admin-resteasy-client/deployment/src/test/resources/app-mtls-config.properties

  Line 12 in e4cab19

  quarkus.keycloak.admin-client.server-url=https://localhost:${quarkus.keycloak.devservices.port}

And OIDC doesn't know that KC admin has some "config server URL" set. That is the backwards compatibility I have mentioned in the comments:

• quarkus/extensions/keycloak-admin-resteasy-client/deployment/src/test/java/io/quarkus/keycloak/adminclient/deployment/KeycloakAdminClientInjectionDevServicesTest.java

  Line 31 in e4cab19

  // intention of this forced dependency is to test backwards compatibility

• quarkus/extensions/keycloak-admin-resteasy-client/deployment/src/test/java/io/quarkus/keycloak/adminclient/deployment/KeycloakAdminClientMutualTlsDevServicesTest.java

  Line 42 in e4cab19

  // intention of this forced dependency is to test backwards compatibility

We can't start new Keycloak if you are already running one somewhere (because you set the URL). In the past, if you only had Keycloak Admin client and wanted to start the Keycloak, you had to include OIDC extension and configure server URL property manually. We have test that ensures when the URL is not set, we start it:

• https://github.com/quarkusio/quarkus/blob/main/extensions/keycloak-admin-resteasy-client/deployment/src/test/java/io/quarkus/keycloak/adminclient/deployment/KeycloakAdminClientZeroConfigDevServicesTest.java

@sberyozkin I'll close it because I don't see the bug, but if I am missing something, let's open a feature request. Or re-open this bug if you feel strongly about this.

[sberyozkin]

@michalvavrik Oh yeah, sorry for the noise, thanks for closing it

[michalvavrik]

np