Can I instruct Socialite to use a proxy for Twitter oAuth1 provider?

[boradatti]

I was setting up Twitter w/ the default provider, initially with these settings:

'twitter' => [
    'client_id' => env('TWITTER_CLIENT_ID'),
    'client_secret' => env('TWITTER_CLIENT_SECRET'),
    'redirect' => env('TWITTER_CLIENT_REDIRECT'),
    'oauth' => 2,
],

Since Twitter is blocked in my country, some of the requests wouldn't come through (cURL error 7), forcing me to do this:

'twitter' => [
    'client_id' => env('TWITTER_CLIENT_ID'),
    'client_secret' => env('TWITTER_CLIENT_SECRET'),
    'redirect' => env('TWITTER_CLIENT_REDIRECT'),
    'oauth' => 2,
    'guzzle' => [
        'proxy' => env('PROXY_SERVER'), // needed locally because geopolitics
    ],
],

This worked! I dd'ed the resulting user and discovered that email is always null for Twitter oAuth2, so I decided to use version 1 instead.

I installed socialiteproviders/twitter, set up the provider and listener as per the docs, and got the below error (also see past issue):

socialiteproviders/twitter SocialiteProviders\Twitter\Provider does not extend Laravel\Socialite\Two\AbstractProvider

I then looked more closely at extendSocialite() and noticed that it accepts a third argument – $oauth1Server, which defaults to null. So I decided to pass \SocialiteProviders\Twitter\Server::class as the third argument, hoping to solve the problem. I also changed oauth => 1 in the service config.

However, I am now getting the error I was getting at the very beginning:

cURL error 7: Failed to connect to api.twitter.com port 443 after 2053 ms: Couldn't connect to server

I suspect this means that extendSocialite() has run successfully, but the request client is no longer using the proxy specified in the config. I could be wrong.

Please help.