On 30 Oct 2014, at 19:13, Lucas Holmquist <lholmqui(a)redhat.com> wrote:
> On Oct 30, 2014, at 9:41 AM, Matthias Wessendorf <matzew(a)apache.org> wrote:
> Hello team!
> On Thu, Oct 9, 2014 at 4:49 AM, Bruno Oliveira <bruno(a)abstractj.org> wrote:
> 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.
So basically you can use passport to secure your endpoint using openId connect (on top of
oauth2). you login as google user and your secure your endpoint with google access token.
with passport.js you can go the authz code grant way because you store token on server
side. Refresh and access token are never stored in browser app.
On native app we’re doing what passport.js is doing but directly on device… not sure there
is anything interesting to demo on native app, it’s more a web or cordova thing. I would
say either use key cloak/passport Js for web pure app and corodva app or use corodva
native oauth2 plugin.
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 adapters );
+1 on keycloak/passport.js integration
As we said passport itself is not an oauth2 provider. You could couple it with KC or
another interesting integration is OAuth2rize + passport which provides an Oauth2 server.
see , 
I’d love to take a deeper look at this example… wdyt Luke?
> 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
> 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.
> Any thoughts?
>  https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot
> 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
> Matthias Wessendorf
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> aerogear-dev mailing list
aerogear-dev mailing list