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.
1. Create Project > Give Project a name > Create
2. Select "APIs and Auth" > APIs > Select "Google+ API" > Enable Google+ API
3. Back to "APIs and Auth" > Credentials > Add Credentials > OAuth 2.0 Client ID >
4. However, it requires that you first configure the consent screen, so do that...most of it is optional...you can fancy it up if you like.
5. Select "Web Application", then give it a name, then paste the info from your Moodle Oauth2 settings page into the boxes and hit "Create".
6. That should be it.
WM
At the top of that Oatuth settings page in Moodle, there's a link to the Google Developer site you need to create the credentials. See here: http://www.awesomescreenshot.com/image/622020/406b83566e23605c1641210f5fd92829
WM
I apologize if this is obvious and not the problem, but there's a box on the Oauth2 settings page that needs to be checked to "Display buttons on login page"
Go to: Site Admin > Plugins > Authentication > Oauth2
Screenshot: http://www.awesomescreenshot.com/image/621933/c8e6cde26df1d3e3889abe3a2fdb82b8
Good luck,
WM
but, Do I want to know if this works with moodle moblie application ?
About the issue, we don't know what was William's version.php file before the upgrade, so it is not easy to reproduce. I wrote this issue https://github.com/mouneyrac/moodle-auth_googleoauth2/issues/168 to make further investigation. Maybe it could also be a file permission issue as the Moodle.org upgrade process requires to change the auth folder permission. William, if you didn't delete the database table, but only the files, it may have been a permission problem in fact. Note: people can uninstall this plugin from Moodle (I think
Also I would like to add that I appreciate if we could all keep support for this plugin on Github. Not here, and especially not by email, as it does not benefit others. Finally when I maintain this plugin or when I personally answer someone about this plugin, I give you my time. If you appreciate it you can "Favorite this plugin" on this page
I ran into some trouble (see above) on 9/24/2015, when installing an update for this plugin. The update caused trouble and all of my users who had authenticated with this method (just over 500) could not sign into our LMS. We had to convert many of them to manual login (not fun) as we tried to figure out how to fix the problem. Mr. Mouneyrac was helpful in suggesting fixes after I contacted him by email. In the end, I just deleted the plugin folder from the server, installed the latest version of the plugin and it was fixed (there's no uninstall feature with this plugin, so I couldn't uninstall and re-install).
When running, this is a great plugin. If something goes bad...users can't sign in...and that can be a mess. So, install updates with caution.