Geek Answers Handbook

Can the login features installed in the user APIs stop working on April 20?

I am currently using the Users API ( here ) with the Go language in the Google App Engine application. My users receive a warning message when they first grant permissions stating that "OpenID 2.0 for Google Accounts is leaving. Developers should upgrade to OpenID Connect by April 20, 2015." But I can’t find any warnings in the documentation of the user APIs saying that something will stop working, for example, I do everything in other sections regarding OpenID 2.0 ( here ).

I use very little user API code, just to create login URLs:

url, _ := user.LoginURLFederated(c, return_url, "www.google.com/accounts/o8/id")

And to read the email addresses of users, for example:

 u := user.Current(appengine.NewContext(r)) email := u.Email

Is there any need to worry about porting, or will the API continue to process without fail after April 20?

+7
google-app-engine go google-openid
source share
2 answers

So it turns out that the answer is "YES!". Definitely stopped working. In older versions of my website, you get to a page with an error trying to log in. Fortunately, I switched from the User package before the deadline to buggier Google Login for Websites .

+2
source share

Read this information: https://developers.google.com/identity/protocols/OpenID2Migration https://developers.google.com/identity/protocols/OpenIDConnect https://developers.google.com/identity/sign-in/ auth-migration

You may also find this forum helpful.

Applications that use user.LoginURLFederated in conjunction with Google Accounts will stop working. These applications must follow the information in the first link above to proceed.

Applications may continue to use user.LoginURLFederated for use with other third-party OpenID2 service providers.

+6
source share

More articles:


All Articles