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

"..succeed to connect to the selected provider but failed to retrieve your user details.." #184

Open
javascriptonian opened this issue Dec 2, 2015 · 11 comments

Comments

@javascriptonian
Copy link

This error occurs when attempting to login using facebook: "The site succeed to connect to the selected provider but failed to retrieve your user details. If you are using Google, check that your site administrator has enabled the Google+ API in the Google developer console. It is the most common reason for this error."
More information about this error displays: "error/auth googleoauth2/faileduserdetails".

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@javascriptonian
Copy link
Author

Solved it.. Should make sure to have "Require App Secret" set to "No" in facebook app > advanced settings..

@mouneyrac
Copy link
Collaborator

Hi Justin,
thanks for the report and thanks even more for the solution. I was planning to update the Facebook documentation helper (all these oauth2 provider keep changing their settings). Reopinin abd assgning to me so I remember.

@mouneyrac mouneyrac reopened this Dec 9, 2015
@mouneyrac mouneyrac self-assigned this Dec 9, 2015
@mouneyrac mouneyrac added this to the 2.3 release milestone Dec 9, 2015
@ghost
Copy link

ghost commented Oct 26, 2016

Hi guys. I think the solution's no more valid (probably due to API 2.8?). I've followed every hint given in the various issues, but I still get this error: "The site succeed to connect to the selected provider but failed to retrieve your user details. If you are using Google, check that your site administrator has enabled the Google+ API in the Google developer console. It is the most common reason for this error."

"Require App Secret" is set to "No" in facebook app > advanced settings
"Facebook Login" has been added as a product, and valid URI has been given...

Any ideas? Anybody's experiencing such problem?
Google & LinkedIn work fine, but we're experiencing difficulties with Microsoft as well...

@blwright
Copy link

I have the same issue with trying to authenticate using Facebook.

@cthemudo
Copy link

I have the same issue with trying to authenticate using Facebook.
I have Moodle 3.1 and FB API 2.8

@blwright
Copy link

Looking at the Developer Console in Google Chrome,
Facebook redirects back to $server/auth/googleoauth2/facebook_redirect.php?code= with a status code 303, then there is a redirect to $server/login/index.php?code=&authprovider=facebook that results in a 404.
BTW I am running Moodle 3.0.6 and FB API 2.8.

@ahmadghazali
Copy link

Help please, have anyone already fixed it?

@mouneyrac
Copy link
Collaborator

No no one sent a pull request for Facebook API 2.8. It will have to wait for when I will have some free time or someone sending a pull request. That said someone told me one of his client used Lenauth oauth2 plugin and it worked (dont have much more detail but it worth the try, lenthauth seems like a good plugin, and if it works please let us know here so people know of a working alternative). Cheers, Jerome

@blwright
Copy link

BTW - I have the lenauth plugin working, but I would prefer to have this plugin as an option.
The lenauth plugin didn't initially work, but I found a note made by Dmitry Shaposhnikov in the comments section of the lenauth moodle plugin page (Thu, Jul 14, 2016, 10:47 PM). That fixed my issue.

@mouneyrac
Copy link
Collaborator

Thanks for the feedback Brendan :)

@ahmadghazali
Copy link

Okay Thank You ^^

@mouneyrac mouneyrac removed their assignment Mar 31, 2017
@mouneyrac mouneyrac removed the ready label Mar 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants