[8.x] Pusher 6.x+ does not support TLS options anymore

[rennokki]

The problem

Pusher 6.x+ swapped their support from CURLOPT to Guzzle, and removed the TLS options, and this brought a series of issues for TLS users that use self-signed certs in servers like Laravel WebSockets and soketi, locally or in private networks.

Potential fixes

There may be an approach to fix this by overwriting the BroadcastManager class at bootstrapping, but I had to find a way to overcome this by solving it at the root so that it isn't required.

Along the way, pre-6.x Pusher support has to be deprecated, and this might lead to issues in 8.x and should be in 9.x, but at the same time, it should be seen as a fix to support the new Pusher version's client argument.

This PR initializes Pusher with a Guzzle client whose options are defined in config/broadcasting.php. curl_options are no longer used, so in case it's defined, it should be removed:

'pusher' => [
    'driver' => 'pusher',
    'key' => env('PUSHER_APP_KEY', 'app-key'),
    'secret' => env('PUSHER_APP_SECRET', 'app-secret'),
    'app_id' => env('PUSHER_APP_ID', 'app-id'),
    'options' => [
        // ...
    ],
    'client_options' => [
        // You can pass request options: https://docs.guzzlephp.org/en/stable/request-options.html
        'verify' => false, // to disable TLS checks
    ],
],

[francoism90]

@rennokki Many thanks!

This is really helpful and needed to allow self-signed certificates on local/non-production environments. Even on LAN, you may need to use SSL/TLS, including testing.

[GrahamCampbell]

I don't think it makes sense to make this change in Laravel 8. Dropping old versions of the pusher sdk is a major breaking change because of the way it cannot be enforced easily.

[GrahamCampbell]

I'd honestly recommend just not using self-signed stuff. There are ways around this, even for local dev.

[francoism90]

@GrahamCampbell I do understand this is not a support forum, but how should this work for things like this?

[rennokki]

@GrahamCampbell At least would make sense to find a way to be able to initialize the custom Guzzle client passed to the Pusher instance for custom Guzzle options. :)

[taylorotwell]

This will need to go to Laravel 9 (master branch).