As an OAuth provider, no, the built in stuff will not work, so if you want to build an OAuth 2 compatible library, you'll have to jump through some hoops to make this work: store the appropriate keys, store consumer/access/request tokens/secrets.
As a consumer, as long as you use compatible libraries, you will be able to make API calls against Google (and other OAuth 2.0) APIs. It sounds like this is what you are looking to do. -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Thu, Aug 11, 2011 at 11:19 AM, WanderingGAE <weritb...@gmail.com> wrote: > Does the API support OAuth 2.0 yet? I see there is experimental support > for Google API's, but does that mean the GAE oauth lib is 2.0 compliant yet? > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/GdmOPD7js9AJ. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
