Complete rewriting of the code and up-to-date for Google+ Deprecation

Author: Sergio Rabellino

CHANGELOG.md

@@ -1,6 +1,41 @@
 Changelog
 ==========
 
+Release 3.1
+-----------
+* Adapted the google oauth2 provider to the Google+ API removal (March 2019)
+* Unable to add Twitter because not supported by the oauth2-client library 2.x (pls don't ask...)
+
+Release 3.0
+-----------
+* Lead Mantainer change from Jerome Mouneyrac to Sergio Rabellino
+* Updated the League library to v2.2
+* Updated the providers to v2.0
+* REMOVED BattleNet as not supported anymore by oauth2-client library 2.x (pls don't ask...)
+* Unable to add Instagram because does not provide the user email via API (pls don't ask...)
+* Unable to add Amazon because not supported by the oauth2-client library 2.x (pls don't ask...)
+* Code refactoring/cleaning (moodle code guidelines)
+* Font update
+* #165 check https is working
+* #221 guzzle is deprecated
+* #110 - configure for Restrict Domains from which accounts can authenticate ( thanks to simonevr )
+* #110 - configure for not allow create new account ( thanks to simonevr )
+* Fixed missing buttons when loginhttps is enabled
+* Fixed unworking "enable all providers" link when loginhttps is enabled
+* Changed some redirect path, so take care on updating production sites that a change in oauth2 registration should be required
+* Now the profile picture is updated from most providers (Dropbox it's the only missing one)
+* If email address needs to be verified on the provider, an error is shown to the user (code cleaned)
+* Added method get_userinfo()
+* Added option for provider links style visualization
+
+Release 2.4 -> 2.9
+-----------
+* never released
+
+Release 2.3
+-----------
+* Facebook emergency patch
+
 Release 2.2
 -----------
 * #177 Create new button similar to socialsharekit but open source

README.md

@@ -1,8 +1,9 @@
-**No new versions are planned starting from Moodle 3.3:** starting from Moodle 3.3, Oauth2 should be implemented in Moodle core. It will require you to upgrade to Moodle 3.3 and switch to the Oauth2 core authentication (and probably do some migration), but it is a great news as authentication is a really sensible matter and having Oauth2 plugins in core will guarantee their maintenance. So starting from Moodle 3.3 I recommend to use the new Oauth2 core plugins ((https://docs.moodle.org/dev/Better_Office_Integrations_3.3#Core_API_for_managing_Authorized_OAuth_Applications) ). Missing core providers will likely be implemented by someone and publish in Moodle.org plugin repository. There will probably be a new Oauth2 categories in the Moodle plugin repository. wait and see...
+
+**Warning for Moodle 3.3 and later:** starting from Moodle 3.3, Oauth2 should be implemented in core. I suppose it likely will be a system that requires creation of individual plugins for each authentication providers. I won't be supporting this plugin starting the release of Oauth2 implementation in Moodle, so starting 3.3 (https://docs.moodle.org/dev/Better_Office_Integrations_3.3#Core_API_for_managing_Authorized_OAuth_Applications) I recommend to use new plugins using this new Moodle core system. They are likely to quickly be implemented by someone else and publish in Moodle.org plugin repository. There will probably be a new Oauth2 categories in the Moodle plugin repository. 
 
 -
 
-This plugin adds the "Sign-in with Google / Github / Linkedin / Windows Live" buttons on the login page. The first time the user login with a social account, a new Moodle account is created.
+This plugin adds the "Sign-in with Google / Facebook / Github / Linkedin / Windows Live" buttons on the login page. The first time the user login with a social account, a new Moodle account is created.
 
 ### Requirements
 PHP 5.5
@@ -11,7 +12,7 @@ PHP 5.5
 1. add the plugin into /auth/googleoauth2/
 2. Install composer.phar: curl -sS https://getcomposer.org/installer | php
 3. Install the 'vendor' folder: php composer.phar install
-4. apply the changes listed in VENDOR CHANGES.md
+4. apply the changes listed in VENDOR CHANGES.md (if any)
 5. run the Moodle upgrade
 6. in the Moodle administration, enable the plugin (Admin block > Plugins > Authentication)
 7. in the plugin settings, follow the displayed instructions.
@@ -21,24 +22,17 @@ If you have any issues you can follow the Git chapter of my free mini-course [ho
 
 ### Implement your own provider (for devs)
 1. add your third party provider for Oauth2 client as explain in https://github.com/thephpleague/oauth2-client
-2. create /classes/provider/newprovidername.php and newprovidername_redirect.php. Then add the lang strings in /lang/en/auth_googleoauth2.php
-and add the provider name to lib.php:provider_list (if you have time you can change the function logic to automatically load the classes from the provider folder
-and then send me a pull request, thanks :))
-
-### Use the table access token (for devs)
-In order to store the user access tokens, you must set the config with:
-set_config('saveaccesstoken', 1, 'auth/googleoauth2');
-
-Then you can use them in your own plugin. The Oauth2 plugin also trigger an event on login.
-You can retrieve the access token from it too.
+2. create [PLUGIN_HOME]/classes/provider/newprovidername.php and  [PLUGIN_HOME]/newprovidername_redirect.php. Then add the lang strings in /lang/en/auth_googleoauth2.php.
 
 ### Composer (for devs)
 The plugin does not include the 'vendor' folder as explained by [composer best practice](https://getcomposer.org/doc/faqs/should-i-commit-the-dependencies-in-my-vendor-directory.md).
 If you need to know more about composer, you can read [Composer Namespaces in 5 Minutes](https://jtreminio.com/2012/10/composer-namespaces-in-5-minutes/)
 
-### Continuous integration
-[![Build Status](https://travis-ci.org/rabser/moodle-auth_googleoauth2.svg?branch=master)](https://travis-ci.org/rabser/moodle-auth_googleoauth2)
+### Continuous integration, tracker...
+[![Build Status](https://travis-ci.org/mouneyrac/moodle-auth_googleoauth2.svg?branch=master)](https://travis-ci.org/mouneyrac/moodle-auth_googleoauth2)
 [![Codacy Badge](https://www.codacy.com/project/badge/84928dc4c553414786735ba745e57c93)](https://www.codacy.com/app/jerome/moodle-auth_googleoauth2)
+[![bountysource](https://api.bountysource.com/badge/team?team_id=49212&style=raised)](https://www.bountysource.com/teams/oauth2-authentication-plugin-for-moodle/backers)
+
 
 ### Credits
 * [Contributors](https://github.com/mouneyrac/auth_googleoauth2/graphs/contributors)
@@ -49,4 +43,6 @@ If you need to know more about composer, you can read [Composer Namespaces in 5
 * [illuminate contracts](https://github.com/illuminate/contracts)
 * [Symfony EventDispatcher](http://symfony.com/)
 
+### +1 the plugin
+To like the plugin, go to the [Moodle.org repository plugin page](https://moodle.org/plugins/view/auth_googleoauth2), login and click on 'Add to my Favorites'. Find other ways to contribute on the [github plugin page](http://mouneyrac.github.io/moodle-auth_googleoauth2/).