Observing the log, you should see many entries for 'server-one', and 'server-two'.
You should also see two big stacktraces, as the server will try to start up, and fail due to not being able to find the keycloak-server.json file. (The stacktrace should be more descriptive - current error reporting NullPointerException is a bug)
But that's good, it means that keycloak-server subsystem was picked up, and started to get initialized.
Running this results in two additional directories created:
domain/servers/server-one
and
domain/servers/server-two
On 4 November 2015 at 16:35, Marko Strukelj <mstrukel@redhat.com> wrote:_______________________________________________On Wed, Nov 4, 2015 at 4:10 PM, Andrej P <ado.boj.83@gmail.com> wrote:On Wed, Nov 4, 2015 at 3:48 PM, Marko Strukelj <mstrukel@redhat.com> wrote:Can you confirm that you see the following lines in your host-controller.log:
[Server:authentication-server-demosetup] 15:58:23,220 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0021: Registered web context: /auth
[Server:authentication-server-demosetup] 15:58:23,267 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "keycloak-server.war" (runtime-name : "keycloak-server.war")No, this lines are missing in log.That's the root of your problem then. Keycloak server subsystem doesn't seem to be initialized at all.From your config files it follows that your 'authentication-server-demosetup' server is using 'group-authentication' group, and 'group-authentication' group is using 'idbt-ha' profile, and 'idbt-ha' profile contains keycloak-server subsystem declaration ...I see no reason for Keycloak server to not get initialized.I'm sorry to say, but I'm out of ideas. If I were you I would try from scratch with an OOTB domain.xml, and host.xml, and setup up Keycloak server without any additional applications deployed, following the instructions I described previously - just get server-one, and server-two using the same group tied to full-ha profile. That way you should get Keycloak up and running. Then I would slowly evolve the configuration towards what you have now. Somewhere during that process there must be a step, that breaks things, and it's not obvious what that step is.
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user