Issues due to same build base for Keycloak.X and Keycloak Wildfly #10385

psytester · 2022-02-22T12:37:09Z

psytester
Feb 22, 2022

Since Keycloak.X is now officially released and Keycloak Wildfly is the old legacy build, I am surprised to have caught parts that are not Keycloak.X ready.
Is that intentional for the time being, where next six months both builds are released?

The documentation, the help pages and finally the usage are different for Keycloak.X

As seen in discussion #10302, the WebUI displays information that is valid for Keycloak Wildfly, but no longer valid for Keycloak.X

Another example is the ./bin/kcadm.sh script. Both builds (Wildfly & Quarkus) use the same /bin/client/keycloak-admin-cli-17.0.0.jar.
Running it, I see hints about the deprecated path /auth

./bin/kcadm.sh config credentials --help | grep "/auth"

    --server SERVER_URL     Server endpoint url (e.g. 'http://localhost:8080/auth')
  $ kcadm.sh config credentials --server http://localhost:8080/auth --realm master --user admin
  $ kcadm.sh config credentials --server http://localhost:9080/auth --realm master --user admin << EOF
  $ kcadm.sh config credentials --server http://localhost:9080/auth --realm master --user admin --password $PASSWORD
  $ kcadm.sh config credentials --server http://localhost:9080/auth --realm master --client reg-cli
  $ kcadm.sh config credentials --server http://localhost:9080/auth --realm master --client reg-cli --keystore ~/.keycloak/keystore.jks
  $ kcadm.sh config credentials --server http://localhost:9080/auth --realm master --user user --client reg-cli --keystore ~/.keycloak/keystore.jks

Navigation Menu

Repository navigation

Issues due to same build base for Keycloak.X and Keycloak Wildfly #10385

Uh oh!

{{title}}

Uh oh!

Replies: 0 comments

Select a reply

Uh oh!

Issues due to same build base for Keycloak.X and Keycloak Wildfly #10385

Uh oh!

psytester Feb 22, 2022

Replies: 0 comments

psytester
Feb 22, 2022