MVC 谷歌登录 - OpenID 身份验证请求包含未注册的域 [英] MVC google login - OpenID auth request contains an unregistered domain

查看:17
本文介绍了MVC 谷歌登录 - OpenID 身份验证请求包含未注册的域的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

当我今天尝试在我的网络应用程序中通过谷歌登录时,出现该错误:

When I try to login today via google in my web app, I get that error:

400 这是一个错误.

400 That’s an error.

OpenID 身份验证请求包含未注册的域:http://XXX.XXX.XXX/(IP在这里)

OpenID auth request contains an unregistered domain: http://XXX.XXX.XXX/ (IP here)

但是在本地主机上一切正常.更重要的是 - 在其他项目上也一切正常.

But on localhost everything works fine. What is more - on other project also everything works nice.

我使用的是默认 OAuth:

I'm using default OAuth:

OAuthWebSecurity.RegisterGoogleClient();

OAuthWebSecurity.RegisterGoogleClient();

如何解决?

推荐答案

我想在这个线程中添加一些上下文,并为当前被阻止的开发人员提供一个潜在的解决方案.

I would like to add some context to this thread together with a potential solution to developers that are currently blocked.

早在 2 月份,我们宣布弃用OpenID 2.0 (OID2) 计划于 2015 年 4 月发布.我们还宣布,4 月之后将不再接受新的 OID2 依赖方 (RP) 注册**2014 年.

Back in February we announced the deprecation of OpenID 2.0 (OID2) scheduled for April 2015. We also announced that new OID2 relying parties (RPs) registrations** will no longer be accepted after April 2014.

鉴于 API 将在不到一年的时间内关闭,我们的目的是避免新的 RP 与 Google 的 OID2 API 集成.相反,我们建议使用我们认为更安全且更易于实施的 OpenID Connect API.

Given that the API will be shut-down in less than a year’s time, our intention is to avoid having new RPs integrating with Google's OID2 API. Instead, we suggest to use our OpenID Connect API which we consider more secure and easier to implement.

注册已于 5 月 19 日有效关闭(如 Google 的 OID2 开发者文档中所述).所有已经使用 OID2 的 RP 不应受到此关闭的影响.

Registrations were effectively closed on May 19th (as documented in the Google’s OID2 developer documentation). All RPs already using OID2 should not be affected by this the closure.

对于目前正在与我们的 OID2 API 进行集成的开发人员(大概是因为他们错过了我们 OID2 文档中的公告和警告),我们将尽最大努力将注册关闭造成的摩擦降到最低.如果您遇到这种情况,请通过发布注册请求告诉我们6 月 15 日之前.该帖子应包含您的应用程序使用的示例 OID2 请求,如果您不想透露此类信息,请发布电子邮件地址,我们将与您联系.我们计划调查每个案例,并尝试以最佳方式让您畅通无阻.

As for developers currently working on an integration with our OID2 API (presumably because they missed the announcement and warnings in our OID2 documentation), we will do our best to minimize the friction caused by the registration closure. If you are in such situation, please let us know by posting a registration request before June 15th. The post should contain a sample OID2 request used by your application, in case you prefer not to disclose such information, please post an email address and we will reach out. We plan to look into each case and try to get you unblocked in the best possible way.

米格尔.

** OID2 没有用于与身份提供者集成的 RP 的注册程序.RP 与联系 Google OID2 API 时使用的领域值(例如 www.example.com)相关联.因此,如果 RP 的领域值已用于联系我们的 OID2 API,则认为该 RP 已注册".

** OID2 does not have a registration procedure for RPs integrating with an identity provider. RPs are associated to the realm value (e.g., www.example.com) used when contacting Google OID2 API. Thus, a RP is considered "registered" if its realm value has been used to contact our OID2 API.

这篇关于MVC 谷歌登录 - OpenID 身份验证请求包含未注册的域的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆