I’m implementing multi-tenancy on an API server using Keycloak and Quarkus, with Policy Enforcer for authorization, and I need to dynamically switch the OIDC tenant configuration based on the incoming request.

When using Quarkus with dependency quarkus-keycloak-admin-client-reactive and invoking some method which does not return Response how do I get real reason why invocation has failed.

When I access http://<ip-redacted>/auth/ or https://<ip-redacted>/auth/.
I cannot see the Welcome to Keycloak page.

When I access http://<ip-redacted>/auth/ or https://<ip-redacted>/auth/.
I cannot see the Welcome to Keycloak page.

When I access http://<ip-redacted>/auth/ or https://<ip-redacted>/auth/.
I cannot see the Welcome to Keycloak page.

When I access http://<ip-redacted>/auth/ or https://<ip-redacted>/auth/.
I cannot see the Welcome to Keycloak page.

When I access http://<ip-redacted>/auth/ or https://<ip-redacted>/auth/.
I cannot see the Welcome to Keycloak page.

Using the keycloak/keycloak image of the docker repo, which is the Quarkus distribution, in a Kubernetes cluster, I have a question concerning the transaction logs: Do they have to be stored persistently in order for keycloak to start up and function properly after the cluster crashed? Or is it sufficient if the logs are only stored temporarily and hence lost after a cluster restart?
I’ve consulted https://quarkus.io/guides/transaction#jdbcstore but still have this question.

Using the keycloak/keycloak image of the docker repo, which is the Quarkus distribution, in a Kubernetes cluster, I have a question concerning the transaction logs: Do they have to be stored persistently in order for keycloak to start up and function properly after the cluster crashed? Or is it sufficient if the logs are only stored temporarily and hence lost after a cluster restart?
I’ve consulted https://quarkus.io/guides/transaction#jdbcstore but still have this question.