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'd like to allow users on my site to authenticate via StackExchange account. This page says SE OpenID endpoint should be, but I can't log in to any site using this endpoint. On the same sites, the Google OpenID endpoint works fine.

Are there any problems or limitations with SE OpenID provider?

share|improve this question
when you say "any site" which sites are you referring to, specifically? We've tested it with a number of large, popular sites that support OpenID and it works. – Jeff Atwood Jul 31 '11 at 23:14
I've tried it from It fails. – Andrei Petrenko Jul 31 '11 at 23:26 fails too. – Andrei Petrenko Jul 31 '11 at 23:35
I can confirm that fails. It says 'Login Cancelled'. – Soumya Aug 1 '11 at 0:54
@Andrei Can't reproduce a problem on, just signed up for a new account using SE OpenID. – Tim Post Aug 1 '11 at 1:35
up vote 4 down vote accepted seems to fail for purely internal reasons. If you create a new account with an OpenID everything seems fine; the whole exchange works properly from our end so far as I can tell.

After a brief exchange with Andrew Arnott (author of dotNetOpenAuth), it was found that is non-compliant with the OpenID spec; claiming to sign fields it does not actually send. It is impossible to securely complete authentication, so we send them an error (the cause of the "Login cancelled" message).

We only really care to support well written OpenID relying parties, such as...

  • Ourselves (more generally, anybody using dotNetOpenAuth semi-competently)
  • Disqus
  • Typepad
share|improve this answer

You must log in to answer this question.

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