"Missing required paramter" with all Social Auth providers The problem: I've just installed social_auth_google, social_auth_twitter and social_auth_linkedin modules. All the modules are configured (Client ID, Client Secret, and other similar fileds). The modules are installed through composer require ..., so I assume that all dependencies are there, but to confirm here's the list of the enabled modules:


  Social              Social API (social_api)         Enabled   8.x-2.0-beta4
  Social              Social Auth (social_auth)       Enabled   8.x-2.0-beta4
  Social              Social Auth Google              Enabled   8.x-2.0-beta3
                      (social_auth_google)
  Social              Social Auth LinkedIn            Enabled   8.x-2.0-beta1
                      (social_auth_linkedin)
  Social              Social Auth Twitter             Enabled   8.x-2.0-alpha2
                      (social_auth_twitter)


Besides these, composer also installed some non-Drupal packages to vendor directory:


  league/oauth2-client (2.3.0)
  league/oauth2-google (2.2.0)
  abraham/twitteroauth (0.9.2)
  league/oauth2-linkedin (2.1.0)


I've embedded "Social Auth Login" block to "Content" region of /user/login and /user/register pages, and I've got a decent-looking login/register pages as the result.

But the problem is that neither of the embedded authentication providers doesn't work. If I click g+, I get "Error: invalid_request. Missing required parameter: client_id". When I click twitter, I get: "You could not be authenticated, please contact the administrator.". With LinkedIn I get: "You need to pass the 'client_id' parameter".

Obviously I'm missing something... Any help?
I've found the reason for the problem: outgoing proxy. The web server where I have my website installed doesn't have direct internet access, but it uses an outgoing proxy.

Regarding social_auth_twitter - it was my mistake - outgoing proxy was blocking access to api.twitter.com. After configuring the proxy to allow this traffic - Twitter authentication started working as expected.

But regarding the other two (social_auth_google and social_auth_linkedin) - no requests ever reached the proxy, meaning that these modules don't know how to use the proxy.

I've ensured that the proxy is configured correctly:


Environment variables http_proxy, https_proxy, no_proxy, HTTP_PROXY, HTTPS_PROXY, NO_PROXY are configured as needed;
In VirtualHost element (Apache configuration) I'm ensuring that these environment variables are available by setting the appropriate PassEnv lines (mod_env module);
settings.php file contains the appropriate $settings['http_client_config']['proxy']['http'] (and other) configuration.


At the end of the day - everything else (installing and updating modules, etc.) is working normally through the proxy, so proxy configuration isn't the problem. 

It looks that, at least for now, you cannot have social_auth_google and social_auth_linkedin if your web server is behind a proxy. Another very disappointing fact is that there are no any logs in /admin/reports/dblog, so you cannot know that modules are struggling to access their corresponding API endpoints. Hopefully it'll be resolved in future versions. For now you simply have to allow direct access, and remove outgoing proxy completely.