Is Google the only OpenID provider that requires "identifier_select"?

Posted by Skrat on Stack Overflow See other posts from Stack Overflow or by Skrat
Published on 2010-06-10T15:17:53Z Indexed on 2010/06/11 3:52 UTC
Read the original article Hit count: 250

Filed under:
|
|

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.

Here are my questions:

  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?

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.

© Stack Overflow or respective owner

Related posts about php

Related posts about google