OpenID authentication rocks.
I’ve been using TypeKey as the OpenID provider for my domain for a long time now and until today things had gone by without a hitch. But tonight, as I was in a hurry to log in to tarpipe to write a quick workflow to use on my upcoming journey, it just failed me.
Now tonight, of all nights, I became aware that not only has TypeKey undergone some changes, but also tarpipe itself changed something in the authentication page so I was confused for a brief period as to what was failing where. But then I followed the authentication steps and it became obviously clear that TypeKey was the one failing me and having zero time to read all their explanations about the changes they performed (and really annoyed that those changes broke the service they’d been rendering me without any kind of previous warning whatsoever –I’m assuming it is a bug, not a conscious decision, but still, a failing authentication service? Ouch!) I decided to take the only course of action that was available to me on the spot.
So TypeKey is misbehaving but this being OpenID, tarpipe doesn’t really care who authenticates me, as long as they do authenticate me, right?
So I just had to open an account on any other OpenID provider, set up my domain to refer that provider as the one that authenticates me and then everything should work, right?
As it turns out yes, that is all there is to it. I created an account on myOpenID.com (don’t know them at all, maybe it was a good choice, maybe it was a bad choice, I’ll have to look into them more carefully later, but for now I just needed to be able to log into tarpipe and do it NOW), I made the necessary changes to my site to reflect the new authentication provider and voilá, instant gratification! I can now log into tarpipe and create and tweak my workflows at will.
It took me all of 20 minutes, from coming across the problem to solving it. Good heh? :-)