feat: Add explicit 'reverb' support to TenancyBroadcastManager #1431
+24
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds
'reverb'to theTenancyBroadcastManager::$tenantBroadcastersallowlist.Why
Laravel 11 registers Reverb as a distinct driver (
'reverb'). Currently, because it is missing from this allowed list, the manager defaults to caching the Central instance and reuses it in Tenant contexts. This causes authentication failures (403 Forbidden) on private channels due to credential leakage.Impact
This enables out of the box support for Reverb in Laravel 11+.
It eliminates the need for users to implement manual workarounds, such as:
reverbdriver topusherinconfig/broadcasting.php.'reverb'to the static allowlist inAppServiceProvider.