Re: [aerogear-dev] Node.js / Passport.js thoughts (was: Re: OAuth2, OpenID connect and AeroGear)

On Oct 30, 2014, at 3:41 PM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > Hello team! > > On Thu, Oct 9, 2014 at 4:49 AM, Bruno Oliveira <bruno(a)abstractj.org&gt; 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" ([1]), that is protected by Passport.js? > > 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 :) sounds good, not a JS ninja but can help on the documentation part. > > 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 ;-) guess if Passport.js is completely different, we can always extend the generic iOS OAuth2 module we have and provide a Passport.js adapter (as we do with the FB for example)

Thanks, Christos > > 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? > > -Matthias > > > [1] 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[3] and another for > OpenID connect[4]. Fell free to link to your respective project. > > > [1] - > http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog... > > [2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1 > > [3] - https://issues.jboss.org/browse/AGSEC-180 > > [4] - https://issues.jboss.org/browse/AGSEC-190 > -- > > abstractj > PGP: 0x84DC9914 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev