-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't replicate Facebook demo. FB requiring HTTPS #510
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
There's no practical way to serve https from localhost, so I think the best resolution will be to switch to an alternative auth flow, like the device flow. I'll work on updating the demo. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I strongly suspect the reason I'm getting a bad request error from the Facebook API when trying to replicate results from the Facebook demo for requesting a token via OAuth2.0 is that they have changed their policy about allowing redirects not over HTTPS. So additional configuration may be required for this to work properly.
Per Facebook's docs, the toggle for 'Enforce HTTPS' that could previously be turned off for apps has been disabled, so OAuth redirects must apparently come with a TLS certificate.
When executing the demo code, an error appears during authentication with Facebook in the browser: "Insecure Login Blocked: You can't get an access token or log in to this app from an insecure page. Try re-loading the page as https://" and R shows a Bad Request error.
The text was updated successfully, but these errors were encountered: