The other problem that's not well defined is how you move from one identity provider to another (particularly if the first one closes down).

ID provider delegation seems to solve this, as long as you have a web page that is stable. For example, I'm editing this via the openid http://kitenet.net/~joey/ (as you can see in RecentChanges), but underneath I'm using myopenid.com as the ID provider. To change it I just update my home page.. --Joey

Joey, this is totally cool! I'm pretty psyched you have this set up. I'm impressed you got it working so nicely. --Evan Prodromou


Gaah. No sooner than I investigate, and get comfortable with, OpenID, do I see something that at first glance appears to be solving the same problem, but (naturally) in an entirely incompatible way: http://bitcard.org.


I had a bit of trouble authenticating to this particular blog via OpenID. When I disabled the extra Simple Registration Extension stuff, I was able to log in. Here's an example URL that was generated after trying to log in:

URL, with parts of it snipped

And here is the error that appeared on the page.

Error: OpenID failure: naive_verify_failed_network:

Apologies if this is the wrong place to report such things.

--Michael Olson

What provider? It seems that perl's openid module does not regognise that url as having authenticated, but I can't debug it until I can reproduce it of course. --Joey

I'm using the pyblosxom OpenID server plugin. It's at http://www.openidenabled.com/software/pyblosxom/pyblosxom-server. I'm authenticating against my own blog instance at http://blog.mwolson.org. --Michael Olson

I'm seeing the same error message as above - interesting is, that I can login to your wiki but not to mine ;)

Guido G√ľnther