Twitter Login States Email/Username already exists

ChadJessen

Hello,

Thank you in advance for all of your help. I am trying to get the twitter extension working and to no avail. I have setup the app and have the correct API Key and secret in place. When I go to login and click the twitter button, it goes through the steps of authorizing access and brings me back to this dialog box.

https://whatsonyourscrubs.com/images/twitter/Twitter-1.JPG

This is what I get when I click the Debug link.

https://whatsonyourscrubs.com/images/twitter/Twitter-Debug.JPG

Here is the link to the Flarum log file.

https://whatsonyourscrubs.com/images/twitter/flarum.log

Here is the link to the webserver log file.

Edited this out in case there was info in there that could lead to a security issue.

I may just have something setup incorrectly. Thank you again for all your help.

Chad

BlackSheep

You can log-in with it but not sign up if your username or email is already taken. I tested it and signing up worked fine for me ! ?

ChadJessen

BlackSheep Alright. I wonder why it doesn't recognize the same email and sign you in like the facebook and google login options do? Thank you for testing it out for me and letting me know it works. I appreciate it!

clarkwinkelmann

Because Twitter accounts don't always have emails, they can't be used as the primary auth factor. Therefore the Twitter user ID is saved and that's what is checked when you login with Twitter.

It's planned to move Facebook/GitHub to that method as well flarum/core897

ChadJessen

clarkwinkelmann Ah I see. That makes more sense now. So I wonder if it would be better to not even use the social media links to log in? Or just use one and not the others?

clarkwinkelmann

ChadJessen indeed. Twitter login doesn't make much sense. Ideally, if you create an account with Twitter and have a validated email at Twitter, you should be able to skip the account validation on Flarum.

But this currently isn't implemented. I think it's also part of the discussion on GitHub I linked above.

PS: actually what I describe was "working" before beta7.1, but not because it was implemented, but because there was a security flaw ?