4

I have tried using my openID and some of the other options and it always says it's an invalid ID...any idea what may be happening?

migrated from meta.stackexchange.com Jul 22 '10 at 17:59

This question came from our discussion, support, and feature requests site for meta-discussion of the Stack Exchange family of Q&A websites.

  • It's not Google is it? – random Sep 12 '09 at 8:35
  • nope it´s not, I don't know what is it – Proxify Sep 12 '09 at 15:16
  • 1
    What's the OpenID and what's your password? – Isaac Waller Sep 28 '09 at 22:13
2

If you do not find an answer in the FAQ (especially the troubleshooting tips) email the team!

0

This was very likely due to a period when the OpenID provider let their security certificate expire. (You are/were using openid.org, I'll bet, Proxify — this has happened more than once, with them.)

When that happens, the Stack Exchange network servers fail to make the HTTPS connection to openid.org, and the signon attempt fails somewhat cryptically. (It'd actually be kind of nice if the site(s) here recognized that it was an HTTPS certificate rejection that was blocking the openid authentication attempt, and returned a more-explanatory message to the user.)

We just went through another period like that, with openid.org, which has fortunately now ended. As of 2012-03-11 openid.org once again has a valid security certificate.

Of course, because their new certificate expires in just 1 year, come 2013-03-13 we'll be in the same mess all over again... unless someone is more on the ball next time, that is.

Personally, now that I finally have access to my stackexchange account again, the very first thing I did was go to "my logins" and add a secondary signon method. Openid.org obviously can't be trusted as a sole provider, which is a shame. (Though it was definitely my fault for making them a single point of failure for my login, in the first place.)

  • 3
    This is also a two and a half year old question.. – cutrightjm Mar 19 '12 at 17:16
  • Yes it is. But one for which no actual answers (or even possible explanations) were provided, which would have left anyone with the same issue who finds it kind of un-helped. Which would be OK, if it were unlikely that anyone WOULD be arriving here with the same issue. Unfortunately, as I explained, this problem is going to come up for openid.org users every time they drop the ball and let their security certificate expire. That's already happened several times in the past, and there's unfortunately no reason to think it might not happen again. The latest certificate expires on 2013-03-13... – FeRD Apr 23 '12 at 8:33

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .