Based on the reasons given, it sounds like a reasonable step to remove WordPress as a standard selection option (although with a less than optimal short notice!).
However, having to type in something manually each time will be a pain, so I would suggest that you replace the button with a "My Favorite OpenID Provider" button, which then fills in a user ...
Managed to add new Stack Exchange OpenID to my Stack Overflow account this way:
Create new stackexchange account
Login on https://openid.stackexchange.com/account/login to reach https://openid.stackexchange.com/user and click the "Use your own URL to log in" link
Then copy the copy the url from the second entry similar to: https://openid.stackexchange.com/...
Even though we aren't responsible for any third-party support or lack thereof, MyOpenID affects Stack Exchange users, so yes, it is a good idea for us to warn people that they might want to move away from it.
I'm exploring what the best way to reach users who only access Stack Exchange through MyOpenID. We will prompt them in some manner to add an ...
Logins used on the Stack Exchange network (excepting Careers Stack Overflow) in the last 180 days (as of 2013-03-05):
Stack Exchange 105,598
This question has been analyzed, from a technical perspective, over on IT Security.SE: see
Appropriate password requirements for a login (OpenID) service/provider/delegate/thing. (See also Recommended policy on password complexity.)
For instance, I'll highlight my answer, where I argue against going overboard on password restrictions, based upon usability ...
Someone is either playing a joke on you, or doing this to simply rattle you. They've been using your email across a few IP's to create unregistered accounts on random sites, where they basically paste the contents of your profile into a question.
I've deleted four fictitious accounts so far, and I'm on the lookout for more. I've also made sure that the ...
Since you are using Gmail and assuming your email is firstname.lastname@example.org, you can use email@example.com for the test account. Gmail ignores everything after the plus sign, and will redirect all emails send there to your regular account. After you register you will be asked if you want to associate the two accounts, the registration process is smart ...
If you have your own domain and homepage, the best you can do is using that as your OpenID account.
Fortunately you don't need to set up a whole OpenID server there, as OpenID supports delegation. Just register to an OpenID provider which supports delegated accounts (MyOpenID was like this, but fortunately Stack Exchange is also okay), and add the following ...
You don't. Google dropped support for OpenID on April 20th. Presumably they thought this was a great way to celebrate Hitler's birthday.
You can still log into Stack Exchange using Google because we rigged up something to support OAuth - "The New Hotness™" - behind the scenes. It looks like OpenID, mostly, and we make it work for old accounts by ...
Facebook authentication is done via OAuth 2.0, but Data Explorer is currently only set up to handle OpenID authentication. However, most of the heavy lifting is done with the help of DotNetOpenAuth, so adding support for OAuth logins is entirely possible - it just hasn't been done yet.
Since Data Explorer is open source, if someone is really interested in ...
I forget why this was a concern before (it might have been from before the user merging queries were written), but the current reason is just that it hasn't been implemented. Strictly speaking, merging users is possible in Data Explorer, it's just not set up yet to do it automatically in the case you're describing.
I've got a todo item to make sure it's ...
Once upon a time, you used MyOpenID to log in on Stack Overflow. But back in August, you removed that credential from your account, adding instead a Google account and relying on that to authenticate you.
Then, today, you tried to log in with your MyOpenID credentials again. Since those were no longer associated with your account, a new account was created.
For me, clearing the cache did not solve the issue, but clearing the stack exchange cookies did.
Look here for instructions on how to clear cookies from individual websites.
(When I did this, I cleared the cookies for stackexchange, stackoverflow, and superuser.)
You can manually enter the Steam OpenID URL (http://steamcommunity.com/openid) by clicking "Show more login options..." and then putting that URL into the box. Then you should be able to log in with Steam normally, and the accounts will be associated automatically.
Alternatively, you can associate another OpenID account with your account on this site by ...
So, I looked around and found out that yes, both the data explorer and stackexchange.com still have a few obsolete openId providers listed in the login / signup options.
I have pushed fixes to both, which will remove claimId (and a couple of others) that are no longer in operation.
The obsolete openId providers will be gone in the next builds of either.
I've experienced the same issue since about the time the login system for SE sites changed. I finally managed to go around it.
For me the case of this exact issue turned out to be HTTPS Everywhere. Disabling the addon allows for the login to work without issue. Enabling it again afterwards doesn't cause any issues with the rest of the site.
The root cause ...
We now de-emphasize MyOpenID as a login option due to the large number of problems they've been having lately.
You can still sign in with it (provided their end of the bargain works) by typing the URL manually or clicking "Show more login options..." and using the MyOpenID button there as before.
Related: unable to log in using myOpenID.com
We refresh your authentication cookie pretty aggressively to help deter theft - this refresh can happen on any url that needs to know who you are.
I introduced a bug that would access a user's cookie on routes that didn't need it, e.g. a feed of bug questions. The access happened after headers had already been sent, meaning the cookie refresh couldn't take ...
"Log in with Stack Exchange" is for folks who have created one of our own OpenID accounts.
You don't have one of those far as I can tell. You're signing in with your Google account, so choose "log in with Google" instead.
You can see what credentials you have on file with us by going to your profile while logged in and clicking "my logins".
If you want to ...
It's not actually up most of the time even though it's supposed to still be operational.
We don't want to even implicitly encourage people to sign up with myOpenID, so we removed the button. You can still sign in with it (assuming the service works) entering your myOpenID URL manually after clicking "show more login options" on the login page.
Far as ...
Good idea, but I think the phrasing of "Other accounts not found" needs work.
It sounds very negative and almost reads like an error message. For a user with existing accounts and is familiar with Stack Exchange, it shouldn't a problem, but a vast majority of the users who get this message will probably be brand new to Stack Exchange, and I'd be worried ...
When you go to "Add login" from your logins, you can always enter the OpenID provider's URL in the text box provided in the "More login options". For Stack Exchange the URL is openid.stackexchange.com.
I don't want to wait weeks and weeks for a response by using the contact form
You wouldn't have had to wait that long. But I'm happy to answer here instead - it's a common request.
And the answer is no.
You can create an account like this - just log out of everything, and sign up for a new one using completely different credentials. And then never, ever, ...
It seems status-completed, answer from Geoff Dalgas:
The GitHub PR was finally approved and merged:
We probably should stop referring to "OpenID" anything altogether since the term tends to just cause varying amounts of confusion among our users.
In the meantime, we don't make any distinction between actual OpenID providers and everything else because the distinction is largely meaningless. Being technically correct about each specific protocol doesn't ...
The problem was related to our internal DNS servers inside the network. Windows 2008 R2 has a penchant for sending EDNS probes, and some firewalls/servers don't like transmitting/processing them. I've disabled EDNS Probes from the dns servers and tested with my own verisign PIP, and it now works.
Sorry for the inconvenience!
This seems to be unrelated to Stack Exchange OpenId in particular. I've tried several OpenId providers (Stack Exchange, a delegated version, MyOpenId, Blogger, and Wordpress); Disqus gives me that error message you encountered for all of them.
The way you've tried should work.