<div dir="ltr">Sure, I agree, and that’s probably the way to do it.<div><br></div><div>But having an easy-to-download (via Maven Coordinates) and run (java -jar keycloak-swarm.jar) version is also useful in many cases, such as Swarm’s own testing.</div><div><br></div><div>I think Hawkular has even started using the keycloak-swarm.jar for their bits, instead of embedding into Hawkular server.</div><div><br></div><div>-Bob</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 17, 2015 at 6:05 AM, Stian Thorgersen <span dir="ltr"><<a href="mailto:sthorger@redhat.com" target="_blank">sthorger@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Isn't including Keycloak server in the microservice incompatible with the whole idea of microservices in the first place?<div><br></div><div>We recommend that people run a dedicated Keycloak server rather than embedding Keycloak server into their applications.</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On 10 December 2015 at 21:22, Bob McWhirter <span dir="ltr"><<a href="mailto:bmcwhirt@redhat.com" target="_blank">bmcwhirt@redhat.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">For those of you not familiar with WildFly Swarm, it’s a project that intends to support microservices by taking your application components, along with just-enough WildFly, and bundling them all into a standalone uberjar.<div><br></div><div>Keycloak counts as “part of WildFly” since it’s implemented mostly as a WildFly subsystem.</div><div><br></div><div>Therefore, WildFly Swarm now supports adding Keycloak Server to your microservice (we’ve supported the client-adapter for a while now, already).</div><div><br></div><div>To that end, we are also producing an handy, all-in-one uberjar for Keycloak Server.</div><div><br></div><div><a href="http://repository-projectodd.forge.cloudbees.com/snapshot/org/wildfly/swarm/keycloak-server-service/1.0.0.Alpha6-SNAPSHOT/keycloak-server-service-1.0.0.Alpha6-20151210.185045-1-swarm.jar" target="_blank">http://repository-projectodd.forge.cloudbees.com/snapshot/org/wildfly/swarm/keycloak-server-service/1.0.0.Alpha6-SNAPSHOT/keycloak-server-service-1.0.0.Alpha6-20151210.185045-1-swarm.jar</a><br></div><div><br></div><div>Just download that .jar, and `java -jar` it and visit <a href="http://localhost:8080/auth/" target="_blank">http://localhost:8080/auth/</a></div><div><br></div><div>It still uses the H2 database, and by default creates or uses a database located at $PWD/keycloak.db, but you can also use the -Dwildfly.swarm.keycloak.server.db=/path/to/keycloakdatabase property to change that.</div><div><br></div><div>Please feel free to give it a test, and for more information about WildFly Swarm, we hang out in #wildfly-swarm on FreeNode IRC.</div><div><br></div><div>Thanks!</div><span><font color="#888888"><div><br></div><div>-Bob</div></font></span></div>
<br></div></div><span class="">_______________________________________________<br>
keycloak-user mailing list<br>
<a href="mailto:keycloak-user@lists.jboss.org" target="_blank">keycloak-user@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a><br></span></blockquote></div><br></div>
</blockquote></div><br></div>