LightOpenID - 提供商针对其发现信息不匹配的标识符发出断言
这是我使用 LightOpenID 提供程序脚本登录 Stack 后遇到的错误。
OpenID 提供商针对其发现信息不匹配的标识符发出断言。
Assertion endpoint info:
ClaimedIdentifier: http ://sub.mydomain.net/?cgillis
ProviderLocalIdentifier: http ://sub.mydomain.net/?cgillis
ProviderEndpoint: http ://sub.mydomain.net/
OpenID version: 2.0 Service Type URIs:
Discovered endpoint info: [{
ClaimedIdentifier: http ://specs.openid.net/auth/2.0/identifier_select
ProviderLocalIdentifier: http ://specs.openid.net/auth/2.0/identifier_select
ProviderEndpoint: http ://sub.mydomain.net/
OpenID version: 2.0 Service Type URIs: http ://specs.openid.net/auth/2.0/server },]
提供商脚本:https ://gist.github.com/1072612
我应该注意到提供者已将 select_id 设置为 true。如果设置为 false,则一切正常。
This is the error I get after logging into Stack with my LightOpenID provider script.
The OpenID Provider issued an assertion for an Identifier whose discovery information did not match.
Assertion endpoint info:
ClaimedIdentifier: http ://sub.mydomain.net/?cgillis
ProviderLocalIdentifier: http ://sub.mydomain.net/?cgillis
ProviderEndpoint: http ://sub.mydomain.net/
OpenID version: 2.0 Service Type URIs:
Discovered endpoint info: [{
ClaimedIdentifier: http ://specs.openid.net/auth/2.0/identifier_select
ProviderLocalIdentifier: http ://specs.openid.net/auth/2.0/identifier_select
ProviderEndpoint: http ://sub.mydomain.net/
OpenID version: 2.0 Service Type URIs: http ://specs.openid.net/auth/2.0/server },]
Provider script: https://gist.github.com/1072612
I should note the provider has select_id set to true. Everything works if it's set to false.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
基本上,问题在于您为身份 URL 设置了
select_id = true
。如果仅针对 checkid() 返回的 url 将其设置为 false,它将按预期工作。有关如何解决此问题的示例,请参阅存储库中
example.php
中的 __construct() 。您还应该看到提供商 wiki 页面和相关的错误报告
Basically, the problem is that you set
select_id = true
for the identity urls. If you set it to false for only the urls returned by checkid(), it will work as expected.See __construct() in
example.php
from the repository for an example on how can this problem be solved.You should also see the Provider wiki page and a related bug report