I would add that OpenID Connect is an authentication layer on top of OAuth2. When you see a "Login with Google" button in a Web app, this is usually what is used.
On Tuesday, 5 May 2015 12:30:08 UTC-4, Thomas Broyer wrote:
On Monday, May 4, 2015 at 10:09:43 PM UTC+2, Juan Pablo Gardella wrote:Awesome!! About:Twitter and GitHub have custom authentication workflows and are not supported by gwt-oauth2 by default.Is it plugable the "workflow" in the framework?More importantly: OAuth is not about authentication, it's about authorization only <http://oauth.net/articles/authentication/ >I don't think Twitter and GitHub have anything special when used for authorization (obtaining tokens to access their APIs). When used as "authentication" mechanisms, well, they're weak (or more accurately, you won't authenticate the user with them).
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment