You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When connecting to a keycloak instance that has TLS encryption enabled, for example when running in Openshift with a certificate provided by the Service CA, the certificate cannot be provided to the extension and the only option is to set it system-wide which requires elevated privileges to do.
After #37206 is possible to disable TLS verification altogether, but that may not be desired for other extensions.
In addition to that mutual TLS is not possible at all because we cannot set client certificate.
Implementation ideas
Should be something similar to what has been done for oidc client extension in #18012 .
The text was updated successfully, but these errors were encountered:
Description
When connecting to a keycloak instance that has TLS encryption enabled, for example when running in Openshift with a certificate provided by the Service CA, the certificate cannot be provided to the extension and the only option is to set it system-wide which requires elevated privileges to do.
After #37206 is possible to disable TLS verification altogether, but that may not be desired for other extensions.
In addition to that mutual TLS is not possible at all because we cannot set client certificate.
Implementation ideas
Should be something similar to what has been done for oidc client extension in #18012 .
The text was updated successfully, but these errors were encountered: