Keycloak plugin does not work in RH SSO Openshift image
See original GitHub issueDescribe the bug
I added sasl plugin to a RH SSO image (downstream for Keycloak) but the ProtonServer throws an exception on startup - io.vertx.core.VertxException: Key/certificate is mandatory for SSL
(full stack trace).
This seems to happen because of a different server config - diff here. Plugin seems to rely on a configuration options which are not present in configuration file for keycloak/RH SSO on openshift.
To Reproduce
Deploy RH SSO with sasl plugin(.jar I used is hosted here) added to /opt/eap/providers
Observe keycloak pod logs to see an exception mentioned above.
Expected behavior No exceptions in keycloak pod logs. Plugin working as expected.
Additional context I am working on Integreatly project, we would like to use external Keycloak instance because we already deploy one, and we have better control of it (HA configuration, monitoring, etc.).
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (7 by maintainers)
Top GitHub Comments
Closing this, as we will not be able to fix this for the 0.32 release, and the release after that will not have Keycloak installed. (See #4391 )
@lulf I see. Thanks for clarifying.
In our use case the external keycloak will be shared. Also, users of that keycloak will be able to create realms with arbitrary name, so name collision with enmasse is a concern.
I like the idea of a lightweight authservice that would just get/watch MessagingUsers resources. It can be implemented as an external AuthenticationService first, and if you like, it can replace standard AuthenticationService (and built-in Keycloack). I’ll give it a shot in spare time.