it IS possible to get users' email via Twitter v1.1 OAuth but we need a tweak...#719
Open
alexagranov wants to merge 1 commit intoNoamB:masterfrom
Open
it IS possible to get users' email via Twitter v1.1 OAuth but we need a tweak...#719alexagranov wants to merge 1 commit intoNoamB:masterfrom
alexagranov wants to merge 1 commit intoNoamB:masterfrom
Conversation
…y config specifies :email
|
+1 |
1 similar comment
|
+1 |
Contributor
|
the project has moved to https://github.com/Sorcery/sorcery/ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If you peruse this thread: https://twittercommunity.com/t/how-to-get-email-from-twitter-user-using-oauthtokens/558/202
you will find enough information on getting user emails out of Twitter.
Here's a quick summary:
After doing all of that, I was still not getting user email by just setting
email: 'email'in Sorcery's twitter configconfig.twitter.user_info_mapping.Debugging the request Sorcery was making for user info, I found that appending 'include_email=true' to the 'verify_credentials.json' endpoint did the trick.
I looked around for as clean as possible a way to add this but without modifying Sorcery configs, this was the quickest way for me to keep working. Hope it helps out.