solved Just want to confirm OneAll login behavior for imported JR accounts

So, I just want to make sure I understand this. I think I asked this before on the JR4 forum....

I have my JR4 site imported.

On Jr5 site, I will install and configure OneAll Module.

User clicks (say) Facebook login to login. The email they use on Facebook, is the same email as registered on the JR5 site.

1. The user will be asked to agree to TOS
2. The authentication process will see that the email address already exists in JR5, and will authenticate the user to their existing account, NOT create a new one. Correct?

Sorry if I sound like a broken record, I had a bad taste in my mouth w/ the Facebook Connect JR4 module, and I'm hoping OneAll is able to see the existing account.

Thanks again! Hope you're having a great weekend!
B




updated by @ilovehousemusic: 04/20/14 02:26:27PM

Correct - as long as the email address matches.


I understand this, but please be prepared to have issues with OneAll as well - anytime you link up with FB in any way, there will be issues. FB as a "platform" is just too big, and too unstable to be problem free. So just be prepared that:

- sometimes you will not get an email address for a user, even though one is configured in their FB account
- sometimes you will not get an image, even though they have a user image on FB

These are not even issues with OneAll, but are due to the security settings on FB's end. FB has added/modified/changed the security settings so many times, that many (I'd say the majority) of Facebook accounts have not been updated/modified, so they are "stuck" on old config's for their user accounts.

So just a heads up


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

Yeah no problemo. I don't care about the image part, users can re-upload. OK so if it creates a duplicate account/profile what are the steps to correct?

What email will JR5 use then, if FB/OneAll sees the email account, but still creates a new profile/account on the JR5 side?

Just want to wrap my head around the behavior so I know what to do to fix it. I'm assuming in the scenario above, they may not ever be able to use FB to authenticate, if it keeps doing the same thing?

Or, would Linking the account be the answer? Like, link the newly created account to the the existing profile? That might be confusing for the user though.

Just thinking out loud.

Hmmm maybe I'll stay away from FB auth...

This would be a bug - a new account should not be created for an email that already exists in the system (a check is done for this before any account is created).

I'm guessing you are wondering what to do if the user already has an account on your system, and they are using a different email address on FB and choose to signup with FB as a new account. In that case, a new account is created. There is no way for JR to "know" that different email addresses are the same user.

In this case (if I was doing it) you would just let the user use what account they want. If you really don't want them having 2 accounts, you could contact them and ask them what account they want to use, then delete the other.

Hope this helps!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
updated by @brian: 03/08/14 10:02:19AM

^ Or, what if they change their email on the "old" account to use the facebook email used during OneAll auth. Then, re-auth? I suppose there's no guarantees on that as well. I understand though...

A user cannot change their email address to one that is being used by another account.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

Ah right. So I would have to delete the authenticated FB account, change their email on existing account, then have them re-auth. Bah, maybe I'll keep FB auth disabled and just use Gmail and Twitter.

I'll close this thread, thanks for your quick responses @brian!