<div dir="ltr">I, for one, would enjoy seeing Keycloak running on Vert.x. I moved my application from WildFly to Vert.x, and now the only reason I'm still running WildFly is Keycloak.<div><br></div><div>I started working on a full Vert.x Adapter, but eventually decided it was easier to just stick to plain bearer auth. (Also because my front-end is GWT + keycloak.js.)</div><div><br></div><div>Also, any recommendations for securing websockets? I use the browser-side EventBus in Vert.x, which uses websockets to exchange messages with the server. Since I want to be able to pass the accessToken to various Vert.x services, it needs to remain uptodate and not be the one used to establish the connection. I implemented a basic system to handle this in Vert.x, but I assume the same issue would exist for anyone using WebSockets to connect to WildFly.</div><div><br></div><div>Alain</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 8, 2015 at 1:33 AM, Stian Thorgersen <span dir="ltr"><<a href="mailto:stian@redhat.com" target="_blank">stian@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Interesting idea, especially with regards to providers. In general we really do need to improve on how providers are written and configured.<br>
<br>
We shouldn't forget about JEE either though. JEE has a lot to offer application developers that Vert.x doesn't.<br>
<br>
Not convinced we should rewrite Keycloak to run on Vert.x. Instead I'd say we should provide hooks into Vert.x and other containers (JEE) to allow users to write providers in whatever they want.<br>
<br>
The #1 thing to think about for Keycloak 2.0 IMO is customization. What parts should be customizable and how do we best allow users to do that?<br>
<div class="HOEnZb"><div class="h5"><br>
----- Original Message -----<br>
> From: "Bill Burke" <<a href="mailto:bburke@redhat.com">bburke@redhat.com</a>><br>
> To: <a href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br>
> Sent: Thursday, 8 January, 2015 1:44:01 AM<br>
> Subject: [keycloak-dev] Build on top of Vert.x?<br>
><br>
> Don't care that much at all about AIO, but what is compelling to me<br>
> about Vert.x is that it is a polyglot platform. If our SPIs could be<br>
> written in any language and deployed easily this would be a huge win and<br>
> could potential bring together very diverse communities (node.js and<br>
> linux-python-admins).<br>
><br>
> Something to think about for Keycloak 2.0.<br>
><br>
> Bill<br>
><br>
> --<br>
> Bill Burke<br>
> JBoss, a division of Red Hat<br>
> <a href="http://bill.burkecentral.com" target="_blank">http://bill.burkecentral.com</a><br>
> _______________________________________________<br>
> keycloak-dev mailing list<br>
> <a href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br>
><br>
_______________________________________________<br>
keycloak-dev mailing list<br>
<a href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br>
</div></div></blockquote></div><br></div>