6 ms·
So... the problem is that it's too easy to forget your OpenID / its login. I propose that the main reason for this is because browsers (and password-storing ap
by Groxx 16y ago
So... the problem is that it's too easy to forget your OpenID / its login.
I propose that the main reason for this is because browsers (and password-storing applications in general) have practically zero support for OpenID. It's all handled by hand. It's all in your head, and nowhere else.
Sorta reminds me of, oh... browsers before password managers. Far far more people used only a couple username/password combinations, or stored their ones in a text file somewhere. Now that managers are integrated, and secure external ones exist, it's viable to actually be safer with your logins, and many more people do so. And now I rely so heavily on my password manager, I only know a couple key points-of-entry where its data is stored - the rest of my passwords are all randomly generated.
OpenID is essentially the next step, and it's precisely the same end-user problem. Imagine if browsers supported it natively via a profile-like system; pick a profile, and every site you've associated with it is immediately logged in for you. You'd be able to handle multiple people using your computer easily - just enter a password to use that profile, and everything can be switched for you. No need to launch that password manager for every site, you sign in once and everything is automatically connected from that point.
OpenID can be significantly more user-friendly than username + password. It just isn't there yet.
- robconery 16y agoThe problem is less that it's easy to forget - it's more that it's easier to completely lose someone. For instance, you forget your login to HN and you can go through a reminder process - pretty simple. You forget your Open ID you're in a world of pain. Moreover most sites can't help you - the URLs contain (usually) no information about you as a person. So you come to me and say "I don't know my login" or worse: "My Open ID provider is gone". All I can do is shrug. The it becomes a matter of sleuthing: IP addresses, PayPal transactions (if you use them)... and so on. I agree it can be better - but it's technology that when mixed with users is a nightmare.
- Groxx 16y agoSame as email accounts now; lose one, or it goes under, and you're in a world of pain because those handy "forgot password" links are tied to that. Moreover, most sites can't help you - the emails contain (usually) no information about you as a person. All of which is only solved by alternate means of identification. ie, GMail lets you specify a cell phone, many other sites have pseudo-personal questions you have to guess to perform a reset without a password / email, etc. What reason is there that a site can't ask a series of questions to re-point an account to a new OpenID? None of this is any different. At all. The only difference is in managing one OpenID vs widely varying logins on every site on the internet.
- wvenable 16y ago> lose one, or it goes under, and you're in a world of pain because those handy "forgot password" links are tied to that. That requires two failures: you forgot your username/password and you lost your email account. That's not the same as forgetting your OpenID or having the provider go down. If you've got username/password, then email is the alternative means of identification. One of the main points of OpenID is avoid giving alternative means of identification, such as an email address.
- Groxx 16y agoNo. Lose your email, and you lose your account. Your sign-up email is probably in there, and the new "owners" can go click the "forgot password" link.
- dasil003 16y agoYou don't need it, if you remember your login and password then you login and change your email. You're not going to sign up with an email that you've lost.
- Groxx 16y agoYou seem to be under the mistaken assumption that this sort of thing will a) inform you you have lost your email account, and b) will only occur after you've noticed. Give me your email account. I can nearly guarantee you I can have 5 sites with new passwords inside 5 minutes. And that's by hand - anyone serious about this could write a couple scripts to grab dozens of the major sites in seconds.
- dasil003 16y agoI'm under no such impression, I'm just pointing out the obvious flaw in your previous post.
- mcantor 16y agohttp://news.ycombinator.com/item?id=1915686 http://news.ycombinator.com/item?id=1915686 I'm kind of creeped out, honestly.
- Groxx 16y agolol, awesome. Good to see I'm not totally insane in this, then. I honestly fail to see any reason OpenID, precisely as it is now, cannot be significantly easier to use than username + password, and more secure because people can deal with a single, better password. It's harder on websites, granted... but in terms of security, most have been slacking pretty hard as-is. (though that's all the more reason to take it out of their hands...)
- tptacek 16y agoIf you get to stipulate browser support, you can do much more interesting things than OpenID. Not requiring browser support to be viable is part of the point of OpenID and OAuth.
- mcantor 16y agoI think that's what the OP is lamenting: That we've traded one problem (remembering which screen name/e-mail address and password you used to log in) with another one (remembering which OpenID you used to sign up, and dealing with the technical repercussions therein), while there is a seemingly superior solution out there (let the browser(s) handle it).
- Hkaccc 16y agoOn the other hand, authenticating users by their browser is like authenticating passengers by the car they're in.
- Groxx 16y agoWhere am I "stipulating" browser support? I'm saying it could be easier with browser support. Easy enough to the point where people would prefer it, causing everything to support it instead of the anemic few we have now. This is one of those areas where people improving security frequently seem to fail to comprehend human behavior. For OpenID to gain critical mass, the average person has to be able to use it simply and correctly enough that they will make the switch. And that implies incredible simplicity. OpenID has the capability, but it seems implementers go out of their way to make the process anything but simple, so people get confused and leave for a lock-in solution like Facebook that has a single button to press. You get people to improve their habits by being easier than their old habits, not by telling them their old habits are dangerous and look, here's a better option. If that worked, people wouldn't be drinking and smoking so much.
- bad_user 16y agoYou actually keep your passwords in your browser's password manager? That's a single point of failure btw. It is actually a lot better to spread your accounts in a couple of buckets (work, personal, sensitive, junk) and remember just those.
- wvenable 16y agoSync your passwords securely to the cloud, single point of failure averted. For maximum security, also set the master password on your browser.
- epochwolf 16y agoActually no, Groxx and I both use 1Password at this time and sync it's database to dropbox. I also have the daily backups turned on in case of database corruption. With dropbox and my backups I have the file in 4 locations at any one time (work laptop, personal laptop, home server, and backup disk)
- darklajid 16y agoThat's not serious, is it? The real point is, that you cannot be sure that you can identify _your customers_. The providers change, you greet them with "Hey, welcome. What do you want to buy here?" instead of saying "Hey, Groxx. Glad you are back. Feel free to use X, Y and Z that you gave us money for in the past". I really like OpenID, but insights like this seriously scare me. And they are _not_ customer friendly when they _don't_ work. Understand that you have no control over that "when" though - you rely on someone else to allow your paying customers to use your (purchased) service.
- Groxx 16y agoThat's the same situation as we have right now, where their login or their email are identical points of failure. Forget one / lose access to your email, and you lose the ability to get back in, so people make a new account. It's not like having usernames and passwords is preventing this. As to providers changing, that's where you allow multiple OpenIDs per person, as fallbacks / alternate ways of signing in. So long as they control one, they can control all. It's not OpenID's fault few sites do this, it's the epic adherence to preferring username + password columns in databases instead of a separate table which would allow for more than one.
- awj 16y ago... except logins and emails are known, understood points of failure that tend to fail closed. If I forget my login I can't access the website, but I can usually go to the website and play email bingo until I hit the one I used. If my email access goes down, I still can't access the website, but I know why and have bigger problems. If I log in with the wrong openid provider ... provider bingo is the ideal case. Otherwise I get in but it looks like my stuff on the website I'm logging into got wiped out. Obviously to most people here it would look more like they used the wrong provider, but that only qualifies openid as a solution for techies. That's a much more serious customer problem from an end-user standpoint. Telling people they can register multiple providers with their account is a band-aid on a bullet wound. And that's just when things are working as intended. Idiot providers, bad implementations, openid servers going down, all of these things add even more potential to screw things up for you.
- Splines 16y agoWhy stop at the browser? I'd love to see a unified ID that persists who I am from when I log on to the computer, check my email, go to HN, and then play some online games. All of this is technically possible, but it's like herding cats.
- zaphar 16y agoI sort of think the problem is that many people have multiple OpenId providers. It sort of reduces half the reason you want to use it. Originally OpenId was a way to have one authentication for multiple services on the net. However when you have a Google Account, A Facebook account, A Twitter account... problems start happening. Which one did you use to login to this service last time? Part of the problem I think is that the providers don't act as consumers also. If I originally had an open id somewhere then why can't I use it for facebook, Google, Twitter, and whatever else. Each "Provider" that offers a service to me which I want forces me to get yet another OpenId. At this point I think I have rougly 4 different OpenId providers and with Google I have like 4 different id's. This gets unwieldy quick. The technology had promise but the way it was rolled out and adopted by various folks caused it to suck a little. Now I need an OpenId manager in my browser like I needed a password manager before. How is this better?
- silencio 16y agoYep, this is my problem, not that I actually forgot all the logins to my individual OpenID provider accounts and variants (but when that happens once in a while, that's also a clusterfuck...). I have one for my domain with myOpenID, I have at least one each through google, yahoo, facebook, twitter, livejournal... every site offering those logins uses any combination of all of those, and I can't remember which OpenID I need to use with the site. This is why I can't even remember the last time I posted on Stack Overflow. I once had to email Jeff Atwood because I had managed to create two accounts with two different identities (this was long ago, before you were able to associate multiple OpenID identities to a single user), and to this day I still don't remember which ones work with the user that has the highest reputation. So I don't even bother logging in most of the time, and choose a random login every time I do. OpenID's biggest end-user benefit was supposed to cut down on the number of disparate accounts people tend to have across multiple websites, and it became moot when everyone and their mother decided that they needed to be the be-all end-all of OpenID providers by turning your login details and identity with that website into an OpenID or OpenID type identity.
- jerf 16y ago"Now I need an OpenId manager in my browser like I needed a password manager before. How is this better?" What you really need is delegation. In a webpage, place in the <head>: <link rel="openid.server" href="openID server URL" /> <link rel="openid.delegate" href="openID server" /> with appropriate values. My OpenID is "http://jerf.org". I delegate that to AOL right now, but I can change that to any provider transparently. (The ickiness of using AOL is mitigated by the trivial way in which I can change it; which of the corporate monstrosities auths me isn't very important, and of the various accounts I have they were the first to be a provider.) Having this implemented by your metaphorical grandmother is obviously a problem. Edit: And also, I'd observe that this solves your personal OpenID problem. It doesn't do a thing to solve the problem for a site trying to use OpenID, such as the original article author, because telling everyone to delegate like this is a boil-the-ocean solution in the context of cutting down support calls.
- mivok 16y agoActually, it seems to me the bigger problem is that some providers just decide to change who they say you are, and those providers (Google) just happen to be the biggest because you're telling users 'just use your google login here'. They don't know anything about openID. Sure, users having multiple OpenIDs is an issue when they forget which they used, but even if this was solved, the other issue seems to be much worse.
- Groxx 16y agoA provider changing their URL: totally agree, huge problem. But that's on the same scale as your email provider changing their URL. Problematic and rare. And it's something nothing can adequately deal with - your "forgot password" links won't work if your email changes domain names. It's also an abnormality that can't be securely accounted for, because otherwise MITMs could just hijack requests and send it to their own servers with no complaints.
- thwarted 16y agoIf we're all going to use SSL to avoid attacks that Firesheep brought to the forefront, users can provide client certificates to different websites, managed on a per-user basis with a passphrase like pass managers work.
- caf 16y agoThe problem with client certificates is that they reside in just one of your browsers - what happens when you want to log in from your girlfriend's PC? You need some method of authorising yourself at new locations, presumably rooted in a username/password somewhere, and you need the UI for that to be dead simple.
- thwarted 16y agoThat same issue exists with a password manager, especially one that exists in the browser. Which is why I suggested client certs need to be managed in some portable manner. Since browsers have started using OS services for certificate management, the portability may be easier. The logging in from your girlfriend's PC is a valid use case, but that's the price you pay for not having to remember passwords. Alternatively, you have an account on your girlfriend's PC that has your certificate store in it. I don't envision the UI for this being any different than for a password manager. In fact, you don't even need more than one certificate, the same cert can be given to every website. Self-signed certs could be used as long as the website only allows login with a single certificate, the server could cache the certificate information as part of the "account" information and only ever allow a single certificate, in the same way ssh keys work (if ssh keys are secure enough is beyond the scope of this discussion). Or for the use-your-girlfriend's-pc scenario, you can bind multiple certificates, stored on different computers, with your account. Account recovery, in the event you need to change the certificate you use, would work just like password recovery, you assert you can't login, the site emails you a link to a page where you can tell it about your new certificate. This is no more or less secure than account recovery with passwords (where access to the email account is proof enough that you are who you are), but the main goal here is to assert to the website your authentication so you don't need to remember different passwords all over the place. I don't think we have a "dead simple" key/cert generation/store right now that would make this work for Joe User, but I think the backend technology is already there.
- joe_the_user 16y agoA) I think you read the first third of the article. The second part goes into the meat of the problem (multiple implementations, providers not being consistent etc). B) Having a browser store everything isn't necessarily a great solution since people may use multiple browsers and public terminals.
- cahit 16y agoForgetting ID/Password is not the only problem with OpenId. The real problem I see is that, you're not only authenticated with your H/Y/GMail user name, but that you have to be authenticated on their servers and open a valid session there without you being aware that it's not closed after you login to the target OpenId site. You still have that open session even if you log out of the target site (or a go-between like ClickPass). For OpenID to work as designed, the user should not have multiple ones and always use the same one wherever an OpenID is requested.
- bdonlan 16y agoIf we're going to push OpenID support into the browser, then why not just use the X.509 client certificate support that's already available?
- Qz 16y agoMozilla was working on that exact thing for Firefox 4 but it got postponed to a later release...