Tags

, , ,

OpenID was supposed to be a web-based single sign-on; however, the conflicts between versions can cause confusion – and prevent sign-on.

When presented with an OpenID sign-on box, you should sign in with:

userid.openidserver.com

For example, with a userid of jdoe at OpenID provider myopenid.com, enter this into the OpenID text box:

jdoe.myopenid.com

(OpenID.net has a more detailed description of the process.)

The problem with using OpenID comes when people try to use OpenID providers like Google.com and Yahoo.com with sites like Toodledo.com: the problem is that Toodledo.com only connects with providers that support OpenID 1.0; there is no message to suggest that the provider does not support that version. Google and Yahoo only support OpenID 2.0; other providers may or may not support OpenID 1.0.

Will Norris has a list of OpenID providers and the features of OpenID they support (broken down by feature). Look for providers that support things like the following:

  • openid-html
  • signon-10
  • sreg-10

Those providers that support these are, I suspect, most likely to support OpenID 1.0 (worked for me!). Also, if you are evaluating these providers in order to choose one, look for a provider that supports a lot of these features of OpenID.

OpenID.net has the specifications for all the versions of OpenID and the features of each.

I chose to go with myopenid.com for my OpenID provider; so far so good – and it works with Toodledo.com (vital!). Another thing – at least with myopenid.com – is that you get an identity page that others can see (I have one).

Another OpenID provider is WordPress.com; if you’ve a login on WordPress.com you have an OpenID. No word on whether WP supports OpenID 2.0.

Advertisements