Skip to content
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

Closed
dcldmartin opened this issue Mar 21, 2018 · 10 comments
Closed

Can't replicate Facebook demo. FB requiring HTTPS #510

dcldmartin opened this issue Mar 21, 2018 · 10 comments
Labels
feature a feature request or enhancement oauth 🏓

Comments

@dcldmartin
Copy link

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.

@braunm

This comment has been minimized.

@kelceywilson

This comment has been minimized.

@aguywithnojob

This comment has been minimized.

@andrex8

This comment has been minimized.

@diegorochawebdg

This comment has been minimized.

@ryancha1205

This comment has been minimized.

@schwarzcrepsley

This comment has been minimized.

@sachinbonzer

This comment has been minimized.

@hadley hadley added feature a feature request or enhancement oauth 🏓 labels Nov 21, 2018
@hadley
Copy link
Member

hadley commented Nov 21, 2018

@hadley
Copy link
Member

hadley commented Nov 23, 2018

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
Labels
feature a feature request or enhancement oauth 🏓
Projects
None yet
Development

No branches or pull requests

10 participants