From 831c3564ec7c209611a1992bb6c40f1c75177efd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pawe=C5=82=20Domas?= Date: Mon, 9 Nov 2015 10:07:24 -0600 Subject: [PATCH] Update tokens.md --- doc/tokens.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/tokens.md b/doc/tokens.md index 38e7543c0..8450958bd 100644 --- a/doc/tokens.md +++ b/doc/tokens.md @@ -82,7 +82,7 @@ the presence stanza that creates the room: to='angrywhalesgrowhigh@muc.example.com/somenickname'> - 0daad82d1ad81c718d643b71b46793af2295bb20e3eb436079e9bbd130ba1ad9_angrywhalesgrowhigh_1446573136000 + 0daad82d1ad81c718d643b7...e9bbd130ba1ad9_angrywhalesgrowhigh_1446573136000 ``` @@ -106,7 +106,8 @@ connection.connect(); In order to start jitsi-meet conference with token you need to specify the token as URL param: ``` -https://example.com/angrywhalesgrowhigh#config.token="0daad82d1ad81c718d643b71b46793af2295bb20e3eb436079e9bbd130ba1ad9_angrywhalesgrowhigh_1446573136000" +https://example.com/angrywhalesgrowhigh#config.token="0daad82d1ad81c718d643b71b46793af2295bb20 +e3eb436079e9bbd130ba1ad9_angrywhalesgrowhigh_1446573136000" ``` At current level of integration every user that joins the conference has to provide the token and not just the one who creates the room. It should be possible to change that by using second anonymous domain, but that hasn't been tested @@ -148,4 +149,4 @@ VirtualHost "jitmeet.example.com" ```lua Component "conference.jitmeet.example.com" "muc" modules_enabled = { "token_verification" } -``` \ No newline at end of file +```