You cannot change the e-mail address attached to your openid.stackexchange account, by design.
If you've lost access to the e-mail you registered with initially, create a new openid.stackexchange account and either add it to your Stack Overflow account (via your profile page, if you're still logged in) or create a new Stack Overflow account and email us via ...
My solution for this. If you have your own domain name, then you can use the delegate feature to set up yourself as your OpenID provider. This way if the OpenID provider you are using decides to shut down, or they have some big security breach, you can very easily switch providers without switching your on all sites that use OpenID. All you have to do is ...
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 ...
I have a feeling this is because Facebook's "basic information" permission includes the friends list, among other general things such as name, profile picture, etc. Stack Exchange probably doesn't access your friends list at all, but that's just what is shown in the permission request.
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
It appears that signing up for Google+ breaks Google Profile OpenIDs.
There's not much we can do from our end, as there's no obvious connection between the old and new identifiers.
If you intend to signup for Google+, you should use a different OpenID provider than Google Profiles. If you're already locked out, create a new account using the top-level ...
There is no such thing as a "regular Stack Exchange account". Stack Exchange recently also became an OpenID provider though.
So to convert your account to Stack Exchange OpenID is as simple as
register on Stack Exchange OpenID
change one of your OpenID accounts in your user info (or add the Stack Exchange one if you only have one OpenID account ...
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 ...
First off: OpenID (and OAuth, which SE uses to support Facebook) is just a way for you to avoid yet another username + password. It does this by letting you say (in effect):
Listen, you don't really need to know who I am. Just ask Google or Facebook or Yahoo or my own website - they'll vouch for me.
It doesn't mean I'm giving SE access to my email, or ...
Google appears to be suffering some sort of outage, it's not just a Stack Exchange problem.
As a work around, if you register a new account at openid.stackexchange.com with the same email address that is associated with your Google account you'll be able to login. We auto-magically map up users with the same verified email address basically. Login in via ...
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 ...
Don't forget that Stack Exchange is now an Open ID provider themselves.
If your only use of Open ID happens to be for Stack Exchange, then it's probably worth registering and switching over to the "local" provider.
Just confirming, Kevin & Michael are correct.
There is no way to not ask for those permissions when authenticating against Facebook. The full permission list is here, of note is the description of the read_friendlists permission.
Provides access to any friend lists the user created. All user's
friends are provided as part of basic data, this ...
At which percentage of failed logons would you consider switching to another OpenID provider? Or at least adding a backup?
I use MyOpenID (with StackID as a backup) and Chrome, and I've never had a single problem logging in. Anecdotes don't prove anything.
I'm not sure how StackID is subject to more issues than any other login system they could implement ...
The "correct" solution is to add an alternate OpenID provider to your account when you can access it. If you go to your profile you'll see a "my logins" link (#1 in the image below). Click that and you'll see something like the following dialog:
(Obviously yours will only have one OpenID).
Click on the "add more logins..." link (#2 in the image above) and ...
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.
What has been working for me so far is to log into Blogger itself in a separate tab, and then come back and log into the StackExchange site. The credentials are cached and it won't send you to the login page, you'll just get logged right in.
We've added an easier way to get at the data needed for OpenID delegation.
First, go to the Open ID site for Stack Exchange:
And login. From there, you'll be taken to your profile page. It's also available via the "Profile" button at the top:
The "Use your own URL to log in" link is present below profile information. ...
Your e-mail isn't the key to your account. Your OpenID endpoint name is the key, and those are unique for your accounts. The e-mail address is irrelevant, and does not need to be confirmed, because it was confirmed separately by your openID provider.
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 ...