用户API中内置的登录功能会在4月20日停止工作吗?

huangapple go评论74阅读模式
英文:

Will the login functionality built into the Users API stop working on April 20th?

问题

我目前正在使用Go语言在我的Google App Engine应用程序中使用用户API(这里)。
当我的用户首次授予权限时,他们会收到一个警告消息,上面写着“Google账户的OpenID 2.0即将停用。开发者应该在2015年4月20日之前迁移到OpenID Connect。”
但是我在用户API的文档中找不到任何警告,说明任何功能将停止工作,就像我在其他关于OpenID 2.0的部分中看到的那样(这里)。

我只使用了很少的用户API代码,只是用来创建登录URL,像这样:

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

以及读取用户的电子邮件地址,像这样:

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

我需要担心迁移吗?在4月20日之后,用户API会处理一切而不会出错吗?

英文:

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).

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

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

答案1

得分: 6

请阅读以下信息:
https://developers.google.com/identity/protocols/OpenID2Migration
https://developers.google.com/identity/protocols/OpenIDConnect
https://developers.google.com/identity/sign-in/auth-migration

你可能会发现这个论坛帖子有帮助。

使用user.LoginURLFederated与Google账户一起使用的应用程序将停止工作。这些应用程序需要按照上面第一个链接中的信息进行迁移。

应用程序可以继续使用user.LoginURLFederated与其他各种第三方OpenID2服务提供商一起使用。

英文:

Please 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 post helpful.

Apps that use user.LoginURLFederated in conjunction with Google Accounts will stop working. These apps need to follow the information in the first link above to migrate.

Apps can continue to use user.LoginURLFederated for use with various other third-party OpenID2 service providers.

答案2

得分: 2

所以,结果是“是的!”。明确地停止工作了。当您尝试登录时,我的网站的旧开发版本现在会跳转到错误页面。幸运的是,在截止日期之前,我已经迁移到了 错误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.

huangapple
  • 本文由 发表于 2015年3月31日 23:47:49
  • 转载请务必保留本文链接:https://go.coder-hub.com/29372846.html
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定