What is the migration path to deprecate userinfo.email for Google Cloud Endpoints apps?

I currently have iOS and Android apps that use Google Cloud endpoints pointing to the Google App Engine backend. They have always relied on the https://www.googleapis.com/auth/userinfo.email area , which appears to have been deprecated on September 1st , in favor of the email area.

The problem is that the client libraries (released two days ago, on 8/12!) Generated by endpointscfg.py still seem to hardcode the time-adjusted scope.

On iOS, the google-api-objectivec-client library has a GTM_OAUTH2_USES_OPENIDCONNECT flag that can switch to the corresponding scope, but that flag doesn't seem to be used anywhere.

It would be easy, of course, to manually modify the autogenerated libraries to use the "email" realm directly, and that even seems to work fine with my App Engine backend, but it certainly doesn't seem like the correct way to migrate the migration.

Has anyone else talked about this and found a better way? Leaked in just two weeks and I would prefer my apps not break.

+3


source to share


1 answer


The good news is, your apps won't break. The verbal information on this page is incorrect (and will be corrected). Thanks for pointing out.

The old range (" https://www.googleapis.com/auth/userinfo.email ") is deprecated but will still be supported. We encourage new applications to use the new "email" area (and will update our libraries to do the same).



By the way, the same is true for the https://www.googleapis.com/auth/userinfo.profile area .

+1


source







All Articles