IntenseDebate & OpenID 2.0
We’ve made some changes to our OpenID 2.0 support. Our OpenID integration has been live for some time now and we’ve had some excellent feedback from our users on how to improve it. So we took it back into the lab for a bit of an overhaul and it came out being much more user friendly. We’re pleased to announce that we have enhanced our OpendID 2.0 integration to support more providers. Thanks again for the great feedback!
Posted by Michael Koenig in features
Join 8,663 other subscribers
4 Comments
RSS feed for comments on this post. TrackBack URI
Sorry, the comment form is closed at this time.
IntenseDebate - Official Blog 
yay!
Almost all bugs are disapearing, but why it's still beta?
I want to echo this bug report that IntenseDebate's comment widget is not properly handing delegated identifiers. For instance, I should be able to use http://josephsmarr.com as my OpenID when leaving a comment, which I have delegated to http://jsmarr.myopenid.com. Right now it doesn't work. I think you're probably passing the originally entered OpenID on to the server and not the openid.delegate value from the page you're doing discovery on. This probably affects a lot of OpenID users, so I'd strongly suggest you either fix it ASAP or take down your OpenID support until you have time to fix it. IMO it damages the OpenID movement if you're advertising a broken implementation, which then gives users a bad impression of how well OpenID works in general…
Happy to help if you have any technical questions about how to fix your implementation.
Thanks! js
Thanks for pointing this out Joseph. We're going to assess the current
state of our OpenID support and see which way we want to go with it.