Each OIDC tenant has its own Vert.x WebClient which it uses to discover the metadata, complete authorization code flow, refresh tokens, introspect them.
If a number of tenants is very large, it can impact the resources.
Unfortunately, each tenant may represent a totally independent OIDC provider with its own connection properties.
But, for example, if each tenant is representing an individual Keycloak realm, then all of these tenants may be talking to the same Keycloak server
Implementation ideas
Add a property allowing to share WebClient, reuse it for all tenants
quarkus-bot[bot]
commented
2 weeks ago
Description
Each OIDC tenant has its own Vert.x WebClient which it uses to discover the metadata, complete authorization code flow, refresh tokens, introspect them. If a number of tenants is very large, it can impact the resources. Unfortunately, each tenant may represent a totally independent OIDC provider with its own connection properties. But, for example, if each tenant is representing an individual Keycloak realm, then all of these tenants may be talking to the same Keycloak server
Implementation ideas
Add a property allowing to share WebClient, reuse it for all tenants