On Thu, Oct 30, 2014 at 7:13 PM, Lucas Holmquist <lholmqui(a)redhat.com>
On Oct 30, 2014, at 9:41 AM, Matthias Wessendorf <matzew(a)apache.org>
On Thu, Oct 9, 2014 at 4:49 AM, Bruno Oliveira <bruno(a)abstractj.org>
> Note: Not only for Keycloak, but also compatible with other technologies
> like passport on Node.js.
Great point on being compatible with passport.js! To ensure our OAuth2
client SDKs do work against node.js (w/ passport.js), how about we build a
Node.js based version of our "Shoot-n-Share backend" (), that is
protected by Passport.js?
So to clear up some confusion that might be happening with what passport
is, it is not an OAuth2 server thing.
it’s really just middleware(think of it as a servlet filter for you java
weenies) for express.js, and by using adapters(like a FB or google), it
can secure RESTful endpoints in that express.js app.
I think the thing that we can do here is make a keycloack adapter for
passport, using the OAuth2 protocol( similar to passports FB and google
+1 would be nice to get this in https://issues.jboss.org/browse/AGJS-252
On short term, it would be possible to use their existing adapters for
FB/Google and protect the node.js backend with these adapters, right ?
Sounds like the AGJS-252 is the ultimate solution we want, but I think for
a quick test/verification (or even example) of our Android/iOS OAuth2
clients, using the FB/Google adapters from passprt.js would be a good first
It could be a (simple) a 'clone' of our java version. I think for Luke,
our Node.js pro, it would be a fairly simple task :)
On the client side, the Android/iOS versions of Shoot-n-Share would simply
offer a new upload target for Passport.js, instead of 'just' FB,
Google-Drive and Keycloak.
That way we will also learn how much Passport.js is actually different,
similar to what we learned on how Google/FB are different ;-)
Another interesting aspect of this is that, once we are ready to release
our OAuth2 SDKs, it would be awesome to actually ship a node.js based demo
as well, instead of just a Java-based backend demo. That would clearly
show, our client libs are working across different backend technologies.
> In the end, OAuth2 is just a protocol and
> should support other servers.
> - Should we provide examples for OpenID connect? Or abstractions?
> To track this issue, we have the following Jira and another for
> OpenID connect. Fell free to link to your respective project.
>  -
>  - https://gist.github.com/abstractj/04136c6df85cea5f35d1
>  - https://issues.jboss.org/browse/AGSEC-180
>  - https://issues.jboss.org/browse/AGSEC-190
> PGP: 0x84DC9914
> aerogear-dev mailing list
aerogear-dev mailing list
aerogear-dev mailing list