Warning: user-focused “I just want this damn thing to work” rant ahead.
It’s no secret that I’m a big proponent of OpenID. Last year I took a stand that I would avoid participation on tech-focused blogs that didn’t support OpenID. Shortly thereafter, I discovered that I couldn’t sign into ReadWriteWeb using my Vidoop OpenID.
I contacted Vidoop, and was told:
I’ve done some more troubleshooting with our friends at ReadWriteWeb, the issue is that they aren’t configured to handle “https” (SSL) connections, and we don’t allow OpenID associations with websites who don’t use SSL to verify with us.
This makes sense to me. The main reason I use Vidoop is because of their excellent security and the fact they require a SSL connection is a good thing. I then contacted Richard at ReadWriteWeb; he bounced the issue to his Movable Type consultant, who responded with this:
I have forwarded this on to Byrne at Six Apart. This seems like something that should be supported natively by MT’s OpenID auth module. I will share any feedback that comes back from 6A.
That was in March 2008. It’s now February 2009, and I’m still receiving “An error occurred: The sign-in attempt was not successful; please try again.” when attempting to log in to what should be an easy authentication system for end users.
Why is this so hard? What’s going on?
Let's Connect!