I am trying to create a Feed's importer for Facebook content. I am using Feeds OAuth module to connect establish connection. But it does not seams to work because I am getting
`Unable to authenticate against OAuth 2.0.` error.

Importers fetchers settings looks like this:

Fetcher : HTTPS OAuth 2.0 Fetcher
Site identifier: http://mysite.aws.af.cm/feeds/oauth/callback/fb
Consumer key: 5622496********
Consumer secret: 007918f**********************
Access token URL: https://graph.facebook.com/oauth/access_token
Authorize URL: https://graph.facebook.com/oauth/authorize

And the facebook API settings looks like this:

Website with facebook login: http://mysite.aws.af.cm/feeds/oauth/callback/fb
What could be the case? Why is the connection not working?

Comments

infojunkie’s picture

I will try it myself and let you know.

infojunkie’s picture

Category: support » bug
Status: Active » Fixed

Facebook support was broken, but I've fixed it in the latest dev.

Your settings are mostly correct. Here are some differences:
* The site identifier should be just fb, not the whole URL. Not sure if you meant this.
* The Fb application should expose the extended permission read_stream.
* The importer should add read_stream to the scope in the OAuth 2 Fetcher settings.

Demo here: http://demos.thereisamoduleforthat.com/feeds/facebook

Please try it and let me know.

koteyka’s picture

It's work fine!
Many thanks to infojunkie!

POVYLAZZZ’s picture

Thank you for the update.
I have tried what you suggested and I have ran into an error:
An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /batch?id=93&op=do StatusText: Internal Server Error ResponseText:

infojunkie’s picture

POVYLAZZZ: make sure you are using the latest dev version and that your installation is done according to the instructions on the module page.

POVYLAZZZ’s picture

Apparently it was a server error the hosting provider I was using had extra limitations on request times.
It is all fine now.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.