Can i use the quarkus-devservices-keycloak as a standalone devservice with quarkus-smallrye-jwt?

[agreedSkiing]

From the pull request #44389 i noticed that there now exists a quarkus-devservice-keycloak artifcat, so... could i use it like below in a pom.xml to start a keycloak deservice without oidc?

        <dependency>
            <groupId>io.quarkus</groupId>
            <artifactId>quarkus-devservices-keycloak</artifactId>
        </dependency>
        <dependency>
            <groupId>io.quarkus</groupId>
            <artifactId>quarkus-smallrye-jwt</artifactId>
        </dependency>

[quarkus-bot[bot]]

/cc @Ladicek (smallrye), @geoand (devservices), @jmartisk (smallrye), @pedroigor (keycloak), @phillip-kruger (smallrye), @radcortez (smallrye), @sberyozkin (jwt,keycloak)

[sberyozkin]

@agreedSkiing It will not work because quarkus-smallrye-jwt would require the key location and the issuer properties, as shown here which can be set by adding some integration between quarkus-devservices-keycloak.

But the lightweight option for smallrye-jwt should be available soon: #44272.

However, I think having a Dev UI experience related to either live or lightweight Keycloak devservice for smallrye-jwt users, similar to what they have for quarkus-oidc makes sense, for example, users would login to Keycloak from the DevUI SPA and then send these tokens to the Quarkus endpoint and smallrye-jwt would verify them...

I think I'll create an enhancement request to track it and discuss with Michal Vavrik further

[agreedSkiing]

but could not find "good" (in my opinion) information about the standalone keycloak devservice on the https://quarkus.io/guides/dev-services#keycloak page

[sberyozkin]

#44272 should offer be a simpler, lighter alternative. Bringing quarkus-devservices-keycloak only to set up those 2 properties will only be more expensive. Which is why I'm thinking of Dev UI related experience which such an intergration can bring.

[agreedSkiing]

Well i think that answer my question it is possible with do it with the "standalone" keycloak devservice, but there will be an easier way in the future :)

[sberyozkin]

@agreedSkiing FYI, there's no standalone devservice, that is a running Keycloak server that those properties expect

[agreedSkiing]

Dang