Google是唯一需要"identifier_select"的OpenID提供者吗? [英] Is Google the only OpenID provider that requires "identifier_select"?

问题描述

我正在用PHP开发OpenID使用者，并且正在使用出色的LightOpenID库( http://gitorious.org/lightopenid ).基于我在示例客户端脚本中找到的代码，我已经成功创建了使用者.但是，我遇到了一个麻烦:Google要求将openid.identity和openid.claimed_id设置为"http://specs.openid.net/auth/2.0/identifier_select"(请参阅

I am developing an OpenID consumer in PHP and am using the fantastic LightOpenID library (http://gitorious.org/lightopenid). Basing my code off of that found in the example client script I have successfully created a consumer. However, I've run across a snag: Google requires the openid.identity and openid.claimed_id to be set to "http://specs.openid.net/auth/2.0/identifier_select" (see here). If I do that it works but other providers (i.e. AOL) don't.

这是我的问题:

1. Google是一个极端的案例吗?–它是唯一需要identifier_select的OpenID提供程序，与OpenID规范相反吗?
2. LightOpenID库是否有缺点?
3. 我对OpenID的工作方式了解不正确吗?
4. 如果Google并不是唯一需要identifier_select的提供商，那么是否有一定数量的我会对其进行硬编码，或者是否可以通过OpenID规范来确定?

1. Is Google a corner case –– is it the only OpenID provider where identifier_select is required, contrary to the OpenID specs?
2. Is there a shortcoming in the LightOpenID library?
3. Is my understanding of how OpenID works incorrect?
4. If Google is not the only provider that requires identifier_select are there a finite number of them which I'll just hardcode in, or is there someway to determine this through the OpenID spec?

我是OpenID内部的新手，所以如果这是一个愚蠢的问题，我不会感到惊讶.搜寻互联网后，我找不到有关此主题的任何信息.

I'm new to the internals of OpenID so I wouldn't be surprised if this is a dumb question. I haven't been able to find any info on this subject after scouring the Internet.

推荐答案

Google并未违反规范. OpenID 2.0规范绝对允许使用identifier_select流，该流启用称为定向身份"的东西，而Google是唯一真正行使此能力的著名OP(据我所知).

Google isn't contradicting the spec. The OpenID 2.0 spec absolutely allows for identifier_select flows, which enable something called "directed identity", which Google is the only notable OP (that I know of) that actually exercises the ability to do.

是的，完全正确地实施的OpenID RP库将自动注意到Google(以及其他类似的OP)需要identifier_select，因为这是在此过程中进行的标识符发现步骤的一部分.抱歉，您使用的是库，但听起来可能是因为OpenID的实现不完整而使您感到悲伤.

And yes, a fully and correctly implemented OpenID RP library will automatically notice that Google (and any other OP like it) requires identifier_select as it's part of the identifier discovery step that picks up on this. Sorry about the library you're using, but it sounds like it's causing you grief due to perhaps being an incomplete implementation of OpenID.

顺便说一下，AOL 确实支持identifier_select.

And by the way, AOL does support identifier_select.

这篇关于Google是唯一需要"identifier_select"的OpenID提供者吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！