Laravel echo - 无法通过私有频道进行身份验证
Posted
tags:
篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了Laravel echo - 无法通过私有频道进行身份验证相关的知识,希望对你有一定的参考价值。
我试图使用私人频道验证laravel回声。每次我得到“无法通过private-basket_details.1验证”。 “basket_details”这是通道名称,1是参数。
当我使用公共频道时,一切都很完美。所以我认为auth部分存在一些问题。
这是我的错误日志
⚠ [14:42:55] - 5eKrT28nX7uLHEkLAAAG could not be authenticated to private-basket_details.1
{
"message": "",
"exception": "Symfony\Component\HttpKernel\Exception\NotFoundHttpException",
"file": "/var/www/html/Laravel/uneek_clothing/trunk/public_html/vendor/laravel/framework/src/Illuminate/Routing/RouteCollection.php",
"line": 179,
"trace": [
{
"file": "/var/www/html/Laravel/uneek_clothing/trunk/public_html/vendor/laravel/framework/src/Illuminate/Routing/Router.php",
"line": 612,
"function": "match",
"class": "Illuminate\Routing\RouteCollection",
"type": "->"
},
{
"file": "/var/www/html/Laravel/uneek_clothing/trunk/public_html/vendor/laravel/framework/src/Illuminate/Routing/Router.php",
"line": 601,
"function": "findRoute",
"class": "Illuminate\Routing\Router",
"type": "->"
},
{
这是我的活动档案。
<?php
namespace App\Events;
use Illuminate\Broadcasting\Channel;
use Illuminate\Queue\SerializesModels;
use Illuminate\Broadcasting\PrivateChannel;
use Illuminate\Broadcasting\PresenceChannel;
use Illuminate\Foundation\Events\Dispatchable;
use Illuminate\Broadcasting\InteractsWithSockets;
use Illuminate\Contracts\Broadcasting\ShouldBroadcast;
use Illuminate\Contracts\Broadcasting\ShouldBroadcastNow;
use App\Basket;
use App\User;
class UpdateWebOrderDetailsToBasket implements ShouldBroadcastNow
{
use Dispatchable, InteractsWithSockets, SerializesModels;
public $basket;
/**
* Create a new event instance.
*
* @return void
*/
public function __construct(Basket $basket)
{
$this->basket = $basket;
}
/**
* Get the channels the event should broadcast on.
*
* @return \Illuminate\Broadcasting\Channel|array
*/
public function broadcastOn()
{
return new PrivateChannel('basket_details.'.$this->basket->id);
}
}
这是我的channels.php
<?php
// use Illuminate\Broadcasting\PrivateChannel;
/*
|--------------------------------------------------------------------------
| Broadcast Channels
|--------------------------------------------------------------------------
|
| Here you may register all of the event broadcasting channels that your
| application supports. The given channel authorization callbacks are
| used to check if an authenticated user can listen to the channel.
|
*/
Broadcast::channel('App.User.{id}', function ($user, $id) {
return (int) $user->id === (int) $id;
});
// Broadcast::PrivateChannel('basket.{basketId}', function ($user, $basketId) {
// return true;
// });
// Broadcast::channel('basket_details.1', function ($user, $basketId) {
// return true;
// });
Broadcast::channel('basket_details.{basketId}', function ($user, $basketId) {
return true;
});
// Broadcast::channel('private-basket_details.*', function ($user, $basketId) {
// return true;
// });
这是我的js文件
Echo.private('basket_details.1')
.listen('.App\Events\UpdateWebOrderDetailsToBasket', (e) => {
console.log("channel started here");
});
这是我的BroadcastServiceProvider
<?php
namespace App\Providers;
use Illuminate\Support\ServiceProvider;
use Illuminate\Support\Facades\Broadcast;
class BroadcastServiceProvider extends ServiceProvider
{
/**
* Bootstrap any application services.
*
* @return void
*/
public function boot()
{
Broadcast::routes();
require base_path('routes/channels.php');
}
}
这是我的laravel-echo-server.json
{
"authHost": "http://192.168.1.120:1002",
"authEndpoint": "/broadcasting/auth",
"clients": [
{
"appId": "be17370a567448f7",
"key": "7af893ebfa188744e6317b30a481824f"
}
],
"database": "redis",
"databaseConfig": {
"redis": {},
"sqlite": {
"databasePath": "/database/laravel-echo-server.sqlite"
}
},
"devMode": true,
"host": null,
"port": "9999",
"protocol": "http",
"socketio": {},
"sslCertPath": "",
"sslKeyPath": "",
"sslCertChainPath": "",
"sslPassphrase": "",
"apiOriginAllow": {
"allowCors": true,
"allowOrigin": "http://192.168.1.120:9999",
"allowMethods": "GET,POST",
"allowHeaders": "Origin, Content-Type, X-Auth-Token, X-Requested-With, Accept, Authorization, X-CSRF-TOKEN, X-Socket-Id"
}
}
答案
坚持可能有问题的一件事是你正在监听的事件命名空间。文档显示使用点表示法而不是反斜杠:
Echo.private('basket_details.1')
// change this to '.App.Events.UpdateWebOrderDetailsToBasket'
// or just 'UpdateWebOrderDetailsToBasket' since you are using the default App\Events.
.listen('.App\Events\UpdateWebOrderDetailsToBasket', (e) => {
console.log("channel started here");
});
您能否验证是否达到了正确的授权路线?如果您从以下位置登录,是否有任何打印
Broadcast::channel('basket_details.{basketId}', function ($user, $basketId) {
logger('Basked ID: ' . $basketId);
return true;
});
例如,如果要使用api中间件保护这些路由,则需要使用正确的标头创建Echo实例:
const client = new Echo({
auth: {
headers: {
Authorization: `Bearer ${token}`
}
}
})
另一答案
你忘了取消注释config / app.php中的BroadcastServiceProvider :: class
App\Providers\BroadcastServiceProvider::class
以上是关于Laravel echo - 无法通过私有频道进行身份验证的主要内容,如果未能解决你的问题,请参考以下文章
laravel-echo-server 404 尝试进行身份验证时
使用 socket.io 和 Laravel Echo 时如何保护私有频道?
无法使用 Redis 和 Laravel 5.3 在私有频道上广播通知