<div>I'm working on it. You can track the progress on that ticket, also the scenario you mentioned will be deployed on OpenShift.</div>
<div class="mailbox_signature">
<br>—<br><br>abstractj<br>PGP: 0x84DC9914</div>
<br><br><div class="gmail_quote"><p>On Fri, Nov 14, 2014 at 9:37 AM, Ken Finnigan <span dir="ltr"><<a href="mailto:ken@kenfinnigan.me" target="_blank">ken@kenfinnigan.me</a>></span> wrote:<br></p><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div dir="ltr">Hi Bruno,<div><br></div>
<div>I'm not super familiar with all the various bits of keycloak, but I think that section covers securing the UPS WAR with keycloak.<div><br></div>
<div>I was wondering how UPS would need to be configured if the UPS WAR is on one WildFly and keycloak is on another, with each on completely separate machines? In particular, so that the Admin console knows where keycloak resides to secure itself.</div>
</div>
</div>
<div class="gmail_extra">
<br><div class="gmail_quote">On Fri, Nov 14, 2014 at 6:27 AM, Bruno Oliveira <span dir="ltr"><<a href="mailto:bruno@abstractj.org">bruno@abstractj.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Ken, the goal is to make use of what already exists on KC. See<br>
section 7.2.3<br>
(<a href="http://docs.jboss.org/keycloak/docs/1.1.0.Beta1/userguide/html/ch07.html#d4e718">http://docs.jboss.org/keycloak/docs/1.1.0.Beta1/userguide/html/ch07.html#d4e718</a>)<br><div class="HOEnZb"><div class="h5">
<br>
On 2014-11-14, Ken Finnigan wrote:<br>
> For a "decoupled version", how do you specify the keycloak host/port to UPS?<br>
><br>
> Does it involve "cracking open" the WAR to modify config, or is there a<br>
> system property?<br>
><br>
> On Fri, Nov 14, 2014 at 5:53 AM, Bruno Oliveira <<a href="mailto:bruno@abstractj.org">bruno@abstractj.org</a>> wrote:<br>
><br>
> > Good morning, I was evaluating this issue and was not that hard to<br>
> > decouple UPS from Keycloak to permit people deploy their own KC<br>
> > instance.<br>
> ><br>
> > Changes required:<br>
> ><br>
> > - Remove wildfly-adapter, once it already comes with KC. It doesn't make<br>
> > sense on having it.<br>
> ><br>
> > <dependency><br>
> > <groupId>org.keycloak</groupId><br>
> > <artifactId>keycloak-wildfly-adapter</artifactId><br>
> > </dependency><br>
> ><br>
> > - Decouple the AeroGear theme for Keycloak from auth-module<br>
> ><br>
> > Now, I'm getting the following error: Failed to find LOGIN theme<br>
> > aerogear, using built-in themes =E2=80=94 for a good reason.a<br>
> ><br>
> > - Provide a separated profile for the "decoupled version": into this<br>
> > way, it's up to our developers use the builtin version or decoupled.<br>
> ><br>
> > As soon as I get a feedback on it. I will move forward with the changes,<br>
> > just let me know what do you think.<br>
> ><br>
> > --<br>
> ><br>
> > abstractj<br>
> > PGP: 0x84DC9914<br>
> > _______________________________________________<br>
> > aerogear-dev mailing list<br>
> > <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
> ><br><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br><br><br>
--<br><br>
abstractj<br>
PGP: 0x84DC9914<br>
_______________________________________________<br>
aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></div></div>
</blockquote>
</div>
<br></div>
</blockquote></div><br>