Enabling/Disabling preview features at startup with Keycloak.X #10986
Replies: 3 comments 4 replies
-
|
There is also the option of |
Beta Was this translation helpful? Give feedback.
-
|
When using the old system-property approach, for several features (at least those depending on EnvironmentDependentProviderFactory, there is an inconsistency in the Admin UI: Features are displayed as active, but the required providers are not there. For example, if I provide a script named my-script-authenticator.js and enable the But if I don't enable the feature at build time and use the system property |
Beta Was this translation helpful? Give feedback.
-
|
Need help in enabling the script feature. I have mapped the script feature using the environment variable. Attached is the complete dockerfile. Built an image based on that and still under Authentication - > Add Execution step, I don't see an script option to create Javascript. Do I need to add the javascript as well under the /opt/keycloak/providers/ during the build stage itself. |
Beta Was this translation helpful? Give feedback.
-
That's exactly what I did - at least it worked with kc 17.0.0. Actually you need to provide a jar file in the providers directory - it is described here and in previous sections: https://www.keycloak.org/docs/latest/server_development/#deploy-the-script-jar |
Beta Was this translation helpful? Give feedback.
-
|
Thanks Daniel, did those steps and can see my authentication js under Add Execution step. They made us to create extra jar file and push it to the providers folder for security purposes it seems. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Daniel,
If you have those details like the steps, could you please share it with
me? It would help me in trying for version 18.
…On Mon, 1 Aug 2022 at 21:40, Daniel Fesenmeyer ***@***.***> wrote:
Do I need to add the javascript as well under the /opt/keycloak/providers/
during the build stage itself.
That's exactly what I did - at least it worked with kc 17.0.0.
—
Reply to this email directly, view it on GitHub
<#10986 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AP4YZ5I3RPBQTP6S3FTJ7E3VW7ZIPANCNFSM5R6XXBXA>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Regards,
Arulaln A R
+91-8754438576
|
Beta Was this translation helpful? Give feedback.
-
|
Got the link, let me try to do the same and get back. Thanks for your help, really appreciate it. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
this issue is related to discussion 10886.
We are currently migrating to Keycloak.X and we use the following system properties to enable preview features at runtime (startup):
We don't set all of those system properties for all of our customers. Instead, each customer gets a subset of those preview features.
We still use the system-property approach documented for the Wildfly distribution, and it works fine with Quarkus - just because we don't use any feature which depends on an EnvironmentDependentProviderFactory, such as scripts.
The question is whether this system-property approach will be still supported, when Wildfly support is dropped? Otherwise, we would have to switch to the approach documented here, using the --features build option. But this would lead to the topic described in 10886: we have to either deal with slow startup due to autobuild, build separate images per customer or implement a workaround.
Beta Was this translation helpful? Give feedback.
All reactions