Oauth2 authentication plugin for Moodle (for Moodle 3.2 and earlier)
Maintained by
Sergio Rabellino
Sign-in with an Oauth2 provider. The first time you sign-in, a new account is created.
Comments
Comments are no longer open for new posts. Existing comments remain available to read.
Even facebook, google, windows live send the authentication back to moodle, but due to some reason the user is not able to go beyond edit profile page.
All the parameters for GoogleOauth2 have been set correctly via admin panel.
Please suggest what needs to be done.
Please follow http://tracker.moodle.org/browse/MDL-34426: the port of the plugin in core for 2.4.
Thanks to everyone who used it, reported issues and contributed to it.
Thanks for the great plugin. I have been testing this on a development server. The following kept reoccurring: when I tried to authenticate with facebook, it kept telling me that my email address was not verified (in FB) even though I knew that it was verified. I managed to get it working by just commenting out the line in auth.php that generates that error. However, this is probably not a good solution. Any suggestions?
Also, is this plugin stable enough for use on a productiuon server?
James: the plugin will not work on 1.9.
In other words, how to guard against spam accounts?
i dint want to cross post it ...
can youplease help me in rectifying this problem.
Regards
Umesh
He mirado la base de datos y en el campo password del usuario aparece "not cached".
Y eso ha echo que cambie "Escoger un método de identificación" en CUENTAS MANUALES, pero antes cuando cree la cuenta de usuario lo hice en "GOOGLEOAUTH2".
Agradecería su pronta ayuda.
Umesh: the plugin doesn't work in local for the reason that you mentioned. Google is going to check your site, and it is not going to find your local site. Google will refuse to authenticate the user in this case, which quite nice actually.
there is no problem with facebook tough...
kindly help...
the problem : The plugin doesn't work in local mode. Google/Facebook/Messenger Connect authentication will most likely fail in the first redirection, and if you enter the authorization code manually in the URL, it will fail when trying to get the access token. Google will return a Missing authorization error.