此 Openid 错误是什么意思：尝试使用存储的发现信息时出错
我正在尝试使用 django-openid 和 openid 设置应用程序。 我收到以下错误，但我无法找出导致这些错误的原因。
[Fri Jan 29 13:29:20 2010] [error] Generated checkid_setup request to https://www.google.com/accounts/o8/ud with assocication XXXXXXXXXXXXXX
[Fri Jan 29 13:29:26 2010] [error] Error attempting to use stored discovery information: <openid.consumer.consumer.TypeURIMismatch: Required type http://specs.openid.net/auth/2.0/signon not found in ['http://specs.openid.net/auth/2.0/server', 'http://openid.net/srv/ax/1.0', 'http://specs.openid.net/extensions/ui/1.0/mode/popup', 'http://specs.openid.net/extensions/ui/1.0/icon', 'http://specs.openid.net/extensions/pape/1.0'] for endpoint <openid.consumer.discover.OpenIDServiceEndpoint server_url='https://www.google.com/accounts/o8/ud' claimed_id=None local_id=None canonicalID=None used_yadis=True >>
[Fri Jan 29 13:29:26 2010] [error] Attempting discovery to verify endpoint
[Fri Jan 29 13:29:26 2010] [error] Performing discovery on https://www.google.com/accounts/o8/id?id=PrHw_N5_3j1HM
[Fri Jan 29 13:29:26 2010] [error] Received id_res response from https://www.google.com/accounts/o8/ud using association XXXXXXXXXXXXX
看起来 Python 无法使用从 Google 检索到的信息。 这个错误是因为来自Google的数据还是openid的问题？
I'm attempting to setup an app using django-openid and openid.
I'm getting the following errors and I can't figure out what is causing them.
[Fri Jan 29 13:29:20 2010] [error] Generated checkid_setup request to https://www.google.com/accounts/o8/ud with assocication XXXXXXXXXXXXXX
[Fri Jan 29 13:29:26 2010] [error] Error attempting to use stored discovery information: <openid.consumer.consumer.TypeURIMismatch: Required type http://specs.openid.net/auth/2.0/signon not found in ['http://specs.openid.net/auth/2.0/server', 'http://openid.net/srv/ax/1.0', 'http://specs.openid.net/extensions/ui/1.0/mode/popup', 'http://specs.openid.net/extensions/ui/1.0/icon', 'http://specs.openid.net/extensions/pape/1.0'] for endpoint <openid.consumer.discover.OpenIDServiceEndpoint server_url='https://www.google.com/accounts/o8/ud' claimed_id=None local_id=None canonicalID=None used_yadis=True >>
[Fri Jan 29 13:29:26 2010] [error] Attempting discovery to verify endpoint
[Fri Jan 29 13:29:26 2010] [error] Performing discovery on https://www.google.com/accounts/o8/id?id=PrHw_N5_3j1HM
[Fri Jan 29 13:29:26 2010] [error] Received id_res response from https://www.google.com/accounts/o8/ud using association XXXXXXXXXXXXX
It looks like Python can't use the information that is being retrieved from Google.
Is this error because of the data coming from Google or is it a problem with openid?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
唔。这实际上并不是一个致命错误；而是一个错误。当我针对 google 的 OP 标识符（生成有趣的定向标识符的 /accounts/o8/id ）使用 python-openid 消费者示例时，我得到了同样的结果，但它成功登录了。
如果你有一个，这可能会导致一些日志垃圾邮件“使用 google 登录”按钮和库也许可以被智能化，以便在用于 OP 标识符时不尝试使用存储的发现信息，但如果您根本无法登录，则可能是您的问题。
Hmm. That's actually not a fatal error; I get the same thing when using the python-openid consumer example against google's OP Identifier (the /accounts/o8/id one that generates the funny directed identifiers), but it successfully logs in.
That probably causes some log spam if you have a "log in with google" button and the library maybe could be smartenified to not try to used the stored discovery information when it was for an OP Identifier, but if you're not able to log in at all, something else is your problem.
当给定的 URL 是服务器的 URL，而不是声明的标识符时，就会发生这种情况。对于生成它的路径来说，这是一个真正的错误，因为 URL 不能用作标识符，但它会在内部被捕获并用于从服务器请求真实的标识符，因此可以安全地忽略日志消息。尽管如此，错误报告已提交给 GitHub 上的 python-openid 项目，并提出修复建议。
This happens when the URL given is the server's URL, instead of the Claimed Identifier. It's a genuine error for the pathway that generates it, because the URL can't be used as an identifier, but it gets caught internally and used to request a true identifier from the server, so it's safe to ignore the log messages. Nevertheless, a bug report has been submitted to the python-openid project on GitHub, with a proposed fix.