Hi, can you try the following please?
1) download the runtime jar _and_ the deployment jar and place both in the providers directory. Jars available e.g. at [1][2]
2) create a quarkus.properties file in the `conf` folder and add your desired properties for splunk.
3) apply a `build`
4) If the build succeeds, start keycloak.should work (not tested here)
This should do the trick from what I see looking at the splung extension, but at the time of writing we know that this approach in general has some severe limitations, e.g. when the quarkus extension needs transient jars to work correctly you have to add them also (so maybe as of [3] your build would fail with a NoClassDefFoundException and you have to add the splunk-javalogging-library jar also to the providers dir). Another point is this is not applicable to extensions like e.g. quarkiverse-logging-json, as they would add already existing configuration options (in that case it's an "exclusive or" between the quarkiverse logging json and quarkus logging, both use the same config and you could just use one or the other, we use the quarkus one).
Having said that, this approach _should_ work but is experimental, so expect breaking changes to come in the future when we figured out how to apply extensions correctly from a multi-classpath application server to a flat-classpath framework ;)
Best regards,
Dominik