Today we had a meeting to discuss how to handle Keycloak extensions
inside the Operator. And let me try to summarize what we discussed.
At the moment we bundle all the desired extensions inside a Docker
image. That works, but it comes at a price, because we need to
maintain the builds for these extensions, or at least make sure they
During our meeting today we concluded that the desired
state would be to fetch the Jar files from the GitHub releases page. For
example: https://github.com/Doccrazy/keycloak-protocol-cas/releases. And
also let people provide the URL for their custom extension.
To accomplish this, all the extensions contributions must
distribute a Jar file. Otherwise, they won't be able to use their
extension with the Keycloak Operator.
Does it make sense?
 - https://github.com/integr8ly/sso_plugins_init
I started some development on a closed ticket (
https://issues.jboss.org/browse/KEYCLOAK-6990) in order to add the ability
to load environment variables through theme.properties for custom themes.
I'd need some feedback from you to see if I'm taking the right path here as
this is my first Keycloak dev and I'm not an expert in Java nor Maven.
This is what I've done so far
I'm quite unhappy with the duplication of the maven-surefire-plugin (you
can see that on top of my plugin block, there's an existing
maven-surefire-plugin plugin block) but I did not found other way to bring
an environment variable into the test context.
If someone could give me some feedback here it'd be very much appreciated :)