The system would need to be changed to check if it's a "social" user and if so only require that the connection to the service has been made, that user details are present (name, email, etc) and an identifier is set for the service.
This would also require the settings for the social connections to be set in the .env configuration file to be passed along to the social service (corresponding to an application set up on their side).
http://www.sitepoint.com/social-logins-php-hybridauth http://hybridauth.sourceforge.net/index.html
The system would need to be changed to check if it's a "social" user and if so only require that the connection to the service has been made, that user details are present (name, email, etc) and an identifier is set for the service.
This would also require the settings for the social connections to be set in the
.env
configuration file to be passed along to the social service (corresponding to an application set up on their side).