News for hackers. Stuff that matters.
Re:Users don't like social login by ams6110 on Wednesday March 20, 2013 @07:09PM (#5411252)
On the one hand, I think email addresses are FAR more understandable as "identity" to an average user than URLs are, which to me is the fatal flaw with OpenID. To an "ordinary" user, URLs are websites, not people.

On the other hand people do change identifiers. They change usernames (jsmith gets married and now wants to be jadams) and they change emails (for the same reason, or because they change ISPs or mobile carriers or whatever). ANY authentication process you use should allow the user to change his identifier (or any other personal attribute even gender) at will.

Internally you deal with this by connecting the identifier to an other token that is the real "permanent" identity for the user in your system. But it's one that's never exposed to the actual user. It sounds like your system was using the email address in the order records to identify the customer. That is what your real problem is, not that people change email addresses.

Re:Users don't like social login by Benferhat on Wednesday March 20, 2013 @09:29PM (#5412132)
> But it's one that's never exposed to the actual user.

Why not expose it to the user? Because then they'll want to change it? Are you talking about browser fingerprinting?

We already expose this on the user/email level, where users can link and log in with as many email addresses as they like, under one account (identifier).

Re:Users don't like social login by garethadams on Thursday March 21, 2013 @07:40AM (#5414365)
You tell your users what their primary key is in your database?
Re:Users don't like social login by Benferhat on Thursday March 21, 2013 @01:39PM (#5417199)
Sure, sometimes their usernames are their primary keys. Even if the actual primary key is arbitrary, the primary identity is still exposed to the user, in that they know what their user account is, and which email addresses are linked to it.