Jitsi Meet - 仅允许 JWT token 身份验证并摆脱用户和密码身份验证

Question

在我的 Jitsi Meet Prodody 配置文件中:~/.jitsi-meet-cfg/prosody/config/conf.d

我有以下配置:

admins = {
  "focus@auth.meet.jitsi",
  "jvb@auth.meet.jitsi"
}

plugin_paths = { "/prosody-plugins/", "/prosody-plugins-custom" }
http_default_host = "meet.jitsi"

VirtualHost "meet.jitsi"

authentication = "token"
app_id = "this-is-my-app-id"
app_secret = "FF0AE1DEC0F36167A100CF0C234CF4A5"
allow_empty_token = false

ssl = {
  key = "/config/certs/meet.jitsi.key";
  certificate = "/config/certs/meet.jitsi.crt";
}
modules_enabled = {
  "bosh";
  "pubsub";
  "ping";
  "speakerstats";
  "conference_duration";
}

speakerstats_component = "speakerstats.meet.jitsi"
conference_duration_component = "conferenceduration.meet.jitsi"

c2s_require_encryption = false

VirtualHost "auth.meet.jitsi"
ssl = {
  key = "/config/certs/auth.meet.jitsi.key";
  certificate = "/config/certs/auth.meet.jitsi.crt";
}
authentication = "internal_hashed"

VirtualHost "recorder.meet.jitsi"
modules_enabled = {
  "ping";
}
authentication = "internal_hashed"

Component "internal-muc.meet.jitsi" "muc"
storage = "memory"
modules_enabled = {
  "ping";
}
muc_room_locking = false
muc_room_default_public_jids = true

Component "muc.meet.jitsi" "muc"
storage = "memory"
modules_enabled = {
  "muc_meeting_id";
  "token_verification";
}
muc_room_cache_size = 1000
muc_room_locking = false
muc_room_default_public_jids = true

Component "focus.meet.jitsi"
component_secret = "1380629bfbc47acef63de093bcf231ec"

Component "speakerstats.meet.jitsi" "speakerstats_component"
muc_component = "muc.meet.jitsi"

Component "conferenceduration.meet.jitsi" "conference_duration_component"
muc_component = "muc.meet.jitsi"

这样我就可以通过 jwt token 进行身份验证。

但是如果我不指定任何 token ，例如:

https://jitsi.mydummyserver.com/test

然后我收到以下提示，要求输入用户名和密码:

有没有办法只允许 token 身份验证并完全摆脱该提示？

谢谢!

Answer 1

您可以在 tokenAuthUrl 上设置 token 生成端点在 /etc/jitsi/meet/<fqdn>-config.js文件。

tokenAuthUrl目前没有记录。您可以查看 tokenAuthUrl 的拉取请求here

如果你想在 session URL 不包含 JWT token 时完全重定向，那么你可以在服务器配置中编写一个简单的 Nginx 或 Apache 规则。

因为 session URL 在 https://meet.example.com?jwt=<token> 中格式，Nginx 配置规则就像

location / {

    set $url 1;    

    if ($arg_jwt = ''){
        set $url 0;
    }   

    if ($url = 1){
        return 301 https://$host$request_uri;
    }

    return 301 https://example.com;
 
}

这将重定向到 example.com如果 session URL 不包含 JWT 查询参数，即使用户试图通过附加 jwt 来绕过 Nginx 规则 session URL 末尾的 auery 参数，访问将被拒绝，因为 JWT 无效。