Allow verified access token#377
Closed
enewbury wants to merge 11 commits into
Closed
Conversation
…nto allow-verified-access-token
Author
|
At some point over the next week I'll try to go through and resolve the conflicts, but at least this is available for easy reviewing. |
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
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
2 participants
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.
Allow access_token authorization. This time secured and verified by /debug_token Facebook API call (APP_ID and scopes are compared).
Note I'm pinging some folks at my consultency to do a security review since that seems to be the main thing needed to check if this codepath is safe.
This is a fresh PR rebased off of main which replaces #315 and #174