Reputation: 28929
In our application, we don't use email address as the username/login, and, as a result, we have accumulated a fair amount of accounts that have duplicate email addresses (usually husband/wife pairs who share the same address, but separate accounts in the app).
We'd like to implement OAuth logins (Facebook, Twitter, Google, etc.) as a perk for our users, and we're currently investigating options for refactoring to allow for this.
My question is - is there any way to allow for OAuth logins without forcing each of our accounts to have a unique email address?
Upvotes: 1
Views: 161
Reputation: 6800
I've changed my earlier answer after being provided more insight to the requirement. If I were you, I'd do it like this -
/me
endpoint of the FB graph API to retrieve the user info and the unique user ID.<userID, list of mapped accounts>
entries.)If the user decided to create a new account and logs in via facebook, I'd repeat steps 1-3 and create a new <username, password>
pair and add it to the list of mapped accounts.
Add comments if you want me to elaborate.
Upvotes: 1