Question

我正在使用laravel-echo-server以及Redis和vuejs通过Laravel 5.5中的websocket广播事件。通过公共渠道，它运行良好，并且事件可以正确地广播到客户端。但是，当我将其更改为专用通道时，即使channel.php文件中的回调函数只是返回true并且不包含任何身份验证逻辑，我也会遇到身份验证问题。我正在使用Sentinel身份验证程序包，但不知道这是否是问题。但是正如我所说，当仅返回“ true”时，身份验证问题仍然存在。

当我检查laravel-echo-server时，我看到一条错误消息，内容为“无法通过身份验证，获得了HTTP代码419”。

我读到有些人面临相同的问题，而他们遇到的可能是csrf令牌问题或专用通道仅适用于集成的auth软件包...等。

我已经在窗口中包含了csrf-token标头。回显配置，但没有结果。

window.Echo = new Echo({
    broadcaster: 'socket.io',
    host: window.location.hostname + ':6001',
auth: {
headers: {
'X-CSRF-TOKEN': $('meta[name=csrf-token]).attr(content)
}
}
});

routes / channel.php

<?php

Broadcast::channel('adminNotify', function() {
    return true;
});

我实际上是为了使ID为1的管理员能够接收事件的：

<?php

use Cartalyst\Sentinel\Laravel\Facades\Sentinel;

Broadcast::channel('adminNotify', function () {
    return (int) Sentinel::check()->id === 1;
});

App \ Events \ NotifyAdminEvent

<?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 App\Ad;
use Sentinel;

class NotifyAdminEvent implements ShouldBroadcast
{
    use Dispatchable, InteractsWithSockets, SerializesModels;

    public $ad;

    public function __construct(Ad $ad)
    {
        $this->ad = $ad;
    }

    /**
     * Get the channels the event should broadcast on.
     *
     * @return \Illuminate\Broadcasting\Channel|array
     */
    public function broadcastOn()
    {
        return new PrivateChannel('adminNotify');
    }
}

app.js

require('./bootstrap');
window.Vue = require('vue');

import Echo from 'laravel-echo';

window.Echo = new Echo({
    broadcaster: 'socket.io',
    host: window.location.hostname + ':6001'
});

laravel-echo-server.json

{
    "authHost": "http://192.168.10.11",
    "authEndpoint": "/broadcasting/auth",
    "clients": [
        {
            "appId": "64fe4c095b0ffb30",
            "key": "9e2bf37f9b3c8c88c3c5f5e207754f1d"
        }
    ],
    "database": "redis",
    "databaseConfig": {
        "redis": {},
        "sqlite": {
            "databasePath": "/database/laravel-echo-server.sqlite"
        }
    },
    "devMode": true,
    "host": null,
    "port": "6001",
    "protocol": "http",
    "socketio": {},
    "sslCertPath": "",
    "sslKeyPath": "",
    "sslCertChainPath": "",
    "sslPassphrase": "",
    "apiOriginAllow": {
        "allowCors": false,
        "allowOrigin": "",
        "allowMethods": "",
        "allowHeaders": ""
    }
}

Laravel日志不记录任何内容，因此我很难知道发生了什么并解决问题。

Answer 1

我已经知道发生了什么。问题出在 laravel-echo-server.json 文件中，并且恰好在第一行“ authHost” 中，而不是放置我的 ip 放置域名。

{
    "authHost": "http://webdev-app.test",
    "authEndpoint": "/broadcasting/auth",
    "clients": [
        {
            "appId": "64fe4c095b0ffb30",
            "key": "9e2bf37f9b3c8c88c3c5f5e207754f1d"
        }
    ],
    "database": "redis",
    "databaseConfig": {
        "redis": {},
        "sqlite": {
            "databasePath": "/database/laravel-echo-server.sqlite"
        }
    },
    "devMode": true,
    "host": null,
    "port": "6001",
    "protocol": "http",
    "socketio": {},
    "sslCertPath": "",
    "sslKeyPath": "",
    "sslCertChainPath": "",
    "sslPassphrase": "",
    "apiOriginAllow": {
        "allowCors": false,
        "allowOrigin": "",
        "allowMethods": "",
        "allowHeaders": ""
    }
}

laravel专用频道和laravel-echo-server的认证问题

1 个答案: