Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

I'm unable to log in with my claim id. It complains that the site maybe a fake vs I'm not sure which end (SO or claim) is broken but can you please advise.

It might even be a security certificate issue on as https: is blocked. I note they seem to have recently updated their interface.

enter image description here

Says cert error in image but whether that means Stack Overflow is now referencing an obsolete endpoint or claim is in error I'm unsure... they don't respond.

share|improve this question
I'm getting this too, on multiple sites. Instead of getting directed to the claimID "login and trust" page, I just get directed to the front page... – naught101 Nov 15 '12 at 11:00
I have this too, fortunately I had cached credentials on SF, so I created new login on stackexchange and added it to on my SF user page. – Hubert Kario Nov 17 '12 at 13:55
Of course, without being able to login, this question is missing a crapload of up-votes – user202483 Nov 19 '12 at 22:47
Indeed, I had to create an account just to vote and comment on this issue – I used to be Vinzz Nov 20 '12 at 16:43
Don't have enough reputation to vote, that's ironic ;o) – I used to be Vinzz Nov 20 '12 at 16:45

Claimid seems to be broken for me, too. If you have cached credentials on any SE site (as Hubert Kario advises), go to your profile → my loginsadd more logins ... and create a new SE login. This will also create a new OpenID through the SE network.

Update, 2012-11-27: Got a note from Terrell Russell at ClaimID. He said the issue was fixed, and indeed it is now. But do try to get as many openids as you can as backup.

share|improve this answer
and if there are no cached credentials? – Michael Piendl Nov 20 '12 at 13:55
indeed, what to do in this case? – I used to be Vinzz Nov 20 '12 at 16:45

I sent a mail to support, and will wait a couple of days for an answer.

After that, I'll try to regain my account throuth StackExchange support, I guess.

Edit: Sent a request through the defunct openID provider workflow:

Everything should be sorted out shortly.

Edit2: See Jeff Atwood's comment there, which claims that claimID isn't doing well. Which may or may not explain why there are login and SSL issues with these guys

share|improve this answer
well, no news from ClaimID support... – I used to be Vinzz Nov 23 '12 at 8:53
I too sent them an email when the problem arose as per some days prior to the date of this questions posting. Today they responded that the problem is resolved. I would recommend now logging in if poss and adding more openids as backups to your account. For me, Googleid is the most trusted due to their scale. – rism Nov 27 '12 at 6:15

You must log in to answer this question.

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