Thanks to Brian Stansberry, I now see that it's quite doable to have the
Keycloak Auth Server installed as part of our subsystem (see below).
Our current approach of copying the WAR into the /deployments directory
will not work in an EAP cluster. In a cluster, there is no /deployments
directory. Instead, you upload your content and tell the domain
controller which nodes to run it on. It makes sense to go ahead and
install as part of the subsystem rather than forcing an administrator to
upload the bits to his system.
So I'm going to go ahead and implement this if there are no objections.
-------- Original Message --------
Subject: Re: [wildfly-dev] Creating a Keycloak Feature Pack
Date: Wed, 10 Sep 2014 16:24:02 -0500
From: Brian Stansberry <brian.stansberry(a)redhat.com>
On 9/10/14, 1:47 PM, Stan Silvert wrote:
*Issue #3: Adding a deployment:* The Keycloak auth server is deployed
as a WAR. We can use the copy-artifacts mechanism to simply copy the
WAR into the deployments directory. But that doesn't work for a domain
where you want to have the WAR pre-loaded into the content repository.
Furthermore, it's probably not the best way to integrate this for
What would be a better option?
See the "A Mixed Approach" section at
The two comments at the bottom of that page are also relevant to that
part of the wiki.
Senior Principal Software Engineer
JBoss by Red Hat
wildfly-dev mailing list