@vanrar68 Did you select the theme by going to Realm Settings -> Themes and choosing the keycloak.v2 theme from the Admin Console Theme setting?
Yes. Worked well with Keycloak distribution but not with Keycloak.X.
keycloak.v2 theme doesn't show up in the admin console dropdown on the Themes tab of the realm settings
I'll run a new Keycloak.X Docker instance from scratch tomorrow and will let you know
Note that I'm passing the --features-admin2 as a argument to the container.
I think the problem you are facing is that build when the container is already running, will have no effect because you need to restart the server.
Easier is to pass any option you want to the container, similar to when using the distribution.
This is one of the main improvements we had if compared with the Wildfly image. Now you have pretty much the same experience when using the distribution and running containers.
Activity
[fixes keycloak#9128] - Enable new admin console to Dist.X
pedroigor commentedon Dec 14, 2021
Original issue #9120.
[fixes #9128] - Enable new admin console to Dist.X
pedroigor commentedon Dec 14, 2021
@chrisx8 Should be fixed, if you are not able to build the project and try it out I can share a docker image.
vanrar68 commentedon Dec 21, 2021
Doesn't seem to work with Keycloak.X 16.1.0
Feature is enabled at startup with --features-admin2 enabled
Following log message appears:
WARN [org.key.com.Profile] (build-12) Experimental feature enabled: admin2
The only themes showing up for admin console are 'base' and 'keycloak'
Keycloak.X runs in dev mode (start-dev) so theme caching is disabled
pedroigor commentedon Dec 21, 2021
@vanrar68 Did you select the theme by going to
Realm Settings->Themesand choosing thekeycloak.v2theme from theAdmin Console Themesetting?vanrar68 commentedon Dec 21, 2021
Yes. Worked well with Keycloak distribution but not with Keycloak.X.
keycloak.v2 theme doesn't show up in the admin console dropdown on the Themes tab of the realm settings
I'll run a new Keycloak.X Docker instance from scratch tomorrow and will let you know
vanrar68 commentedon Dec 22, 2021
Same result with a brain new docker instance. Here's what I do:
Inside the container:
pedroigor commentedon Dec 22, 2021
@vanrar68 It works for me when running:
Note that I'm passing the
--features-admin2as a argument to the container.I think the problem you are facing is that
buildwhen the container is already running, will have no effect because you need to restart the server.Easier is to pass any option you want to the container, similar to when using the distribution.
This is one of the main improvements we had if compared with the Wildfly image. Now you have pretty much the same experience when using the distribution and running containers.
vanrar68 commentedon Dec 22, 2021
Ok thanks, that solves the problem