用户API中内置的登录功能是否会在4月20日停止工作？ [英] Will the login functionality built into the Users API stop working on April 20th?

问题描述

我目前正在使用用户API（这里有这个），我的Go语言Google App Engine应用程序。我的用户在第一次授予权限时会收到警告消息，声明Google帐户的OpenID 2.0即将消失，开发人员应在2015年4月20日之前迁移到OpenID Connect。但是我无法在用户API的文档中发现任何警告，说任何事情都会停止工作，就像我在其他章节中关于OpenID 2.0一样（ here）。

I am currently using the Users API (this one here) with the Go language on my Google App Engine application. My users are getting the warning message when they first grant permissions that says "OpenID 2.0 for Google accounts is going away. Developers should migrate to OpenID Connect by April 20, 2015." But I can't find any warnings in the documentation for the Users API anywhere saying that anything will stop working, like I do all throughout other sections regarding OpenID 2.0 (here).

我只使用很少的用户API代码，只是为了创建这样的登录url： p>

I am using very little of the Users API code, just to create the login urls like this:

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

并阅读用户的电子邮件地址，如下所示：

And to read the users' email addresses, like this:

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

我是否需要担心迁移，或者用户API是否会在4月20日之后处理所有内容？

Do I need to worry about migrating, or will the Users API handle everything without failing after April 20th?

推荐答案

所以，事实证明答案是是！。绝对停止工作。当您尝试登录时，我的网站较早的开发版本会将您带到错误页面。幸运的是，我已将截止日期前的用户软件包移至很多 buggier Google登录网站。

So, it turns out that the answer is "YES!". Definitely stopped working. The older development versions of my website now take you to an error page when you try to sign in. Luckily I had moved away from the User package before the deadline to the much buggier Google Sign-In for Websites.

这篇关于用户API中内置的登录功能是否会在4月20日停止工作？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！