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

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

问题描述

当我尝试通过谷歌登录今天我的web应用程序,我得到这个错误:

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.

早在二月,我们公布的 =htt​​ps://developers.google.com/accounts/docs/OpenID2> OpenID的2.0 (OID2)定于4月到2015年,我们还宣布,新OID2依赖方(RPS)注册**将不再2014年4月后接受

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与谷歌的API OID2整合。相反,我们建议使用我们认为更安全,更容易实现我们的 OpenID的连接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日(如谷歌的OID2开发者文档记录)。所有RP已经在使用OID2不应由该封闭件的影响。

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开发(presumably,因为他们错过了OID2文档在公告和警告),我们将尽最大努力减少因注册关闭的摩擦。如果你是在这样的情况下,请让我们知道通过发布注册申请前6月15日。该职位应该包含您的应用程序使用的样本OID2要求,如果你preFER不披露这些信息,请邮寄的电子邮件地址,我们会伸手。我们计划寻找到各种情况,并尝试让你在尽可能最好的方式畅通。

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有关联(例如,www.example.com)联系谷歌OID2 API时使用的域值。因此,RP被认为是注册如果它的域值被用来联系我们的OID2 API。

** 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天全站免登陆