<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
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). <br>
<br>
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.<br>
<div class="moz-forward-container"><br>
So I'm going to go ahead and implement this if there are no
objections.<br>
<br>
Stan<br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject:
</th>
<td>Re: [wildfly-dev] Creating a Keycloak Feature Pack</td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date: </th>
<td>Wed, 10 Sep 2014 16:24:02 -0500</td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">From: </th>
<td>Brian Stansberry <a class="moz-txt-link-rfc2396E" href="mailto:brian.stansberry@redhat.com"><brian.stansberry@redhat.com></a></td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>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
> standalone either.
>
> What would be a better option?
>
See the "A Mixed Approach" section at
<a class="moz-txt-link-freetext" href="https://developer.jboss.org/docs/DOC-25627">https://developer.jboss.org/docs/DOC-25627</a>
The two comments at the bottom of that page are also relevant to that
part of the wiki.
Cheers,
--
Brian Stansberry
Senior Principal Software Engineer
JBoss by Red Hat
_______________________________________________
wildfly-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a>
</pre>
<br>
</div>
<br>
</body>
</html>