Afraid this is not something we would like to have. HttpClient SPI is
explicitly for obtaining a Apache HttpClient instance configured in config
files rather than in code. Further, JAX-RS client is not used within
Keycloak Server itself as such this is not something we want to support/add.
On Thu, 12 Sep 2019 at 12:33, Dmitry Telegin <demetrio(a)carretti.pro> wrote:
Hi,
We are considering the following improvements to the HttpClient SPI:
- ability to return a JAX-RS client instance in addition to Apache
HttpClient. The former will use the latter as an engine;
- multiple clients with config param overrides (pooling/TTLs/timeouts/etc.)
Just wanted to know if the Keycloak team would be interested in having
this in upstream.
The main purpose is to simplify development of the providers that consume
multiple external REST services. Background: our in-house providers are
currently using ad-hoc ResteasyClient, and there are concerns about thread
safety and code duplication, so we're looking into migrating to the
built-in HttpClient wrapped into JAX-RS client.
Regards,
Dmitry
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev