On Aug 26, 2013, at 12:11 PM, Lucas Holmquist <lholmqui(a)redhat.com> wrote:
We are planning on adding an OAuth2 adapter to the JS library for
1.3.0. We are going to code against the google OAuth2 playground stuff, but trying to
follow the spec as much as possible and try to be as generic as we can.
I'm not sure if this should be an "adapter" or something different. If it
is an adapter of the Authentication plugin( not sure what we are calling the different
pieces. pipeline, data manager, etc.), then we should expect to see authentication
methods( enroll, login, logout ), but i think this "adapter" should be much
more than that.
If implementing those methods is possible, I would like to see this as an Auth adapter but
then with the other useful functionality on top. If not possible, then do you have a
proposal of what an OAuth2 plugin would look like?
It should be used to connect to secured services( api ) that a user allows, such as GCM
for chrome or the google+ platform, or some other enterprisey thing.
I'm wondering if this should be a standalone thing. I kind of like this idea so when
we do social login, which will most likely have OAuth2, we can just access it.
Thoughts?
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev