For more information on the topic of auth, identity and sign-in which was not linked in my last comment, you can also check out the Google Identity Platform <https://developers.google.com/identity/> docs. For more on using OAuth 2.0 to interact with Google APIs, you can check out the API Client Library docs for various languages (java linked <https://developers.google.com/api-client-library/java/google-api-java-client/oauth2> ).
On Wednesday, October 14, 2015 at 6:30:11 AM UTC-4, tempy wrote: > > I have an app that makes extensive use of the Users API + OAuth1. I've > been relying on the unique google identifiers produced by the Users API to > identify my users. Switching to OAuth2 on it's own is not a problem, but I > can't see a way in which Google-Auth-via-OAuth2 is integrated with GAE's > Users API. > > As I understand it, Google is suggesting that migration basically involves > using Google's open-to-all OAuth2 API, which has no special integration > with GAE. Is this correct? If so, then the google ID's that this API will > return will not match the ones that I had previously seen with > UsersAPI+OAuth1, and the app is in trouble, those IDs are keyed to existing > users. > > If this is not the case, then how do I go about using OAuth2 to get the > same google IDs that I've been getting with the UsersAPI+OAuth1 in the past? > > Many thanks! > mike > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/50b197dc-131c-40ea-8a01-643647ff0d43%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
