|
|
@@ -46,7 +46,7 @@ JitsiMeetJS.init(initOptions).then(function(){
|
|
46
|
46
|
|
|
47
|
47
|
In order to start jitsi-meet conference with token you need to specify the token as URL param:
|
|
48
|
48
|
```
|
|
49
|
|
-https://example.com/angrywhalesgrowhigh#config.token="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWV9.TJVA95OrM7E2cBab30RMHrHDcEfxjoYZgeFONFh7HgQ"
|
|
|
49
|
+https://example.com/angrywhalesgrowhigh?jwt="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWV9.TJVA95OrM7E2cBab30RMHrHDcEfxjoYZgeFONFh7HgQ"
|
|
50
|
50
|
```
|
|
51
|
51
|
At current level of integration every user that joins the conference has to provide the token and not just the one who
|
|
52
|
52
|
creates the room. It should be possible to change that by using second anonymous domain, but that hasn't been tested
|
|
|
@@ -109,7 +109,7 @@ VirtualHost "jitmeet.example.com"
|
|
109
|
109
|
-- generator and the plugin
|
|
110
|
110
|
```
|
|
111
|
111
|
|
|
112
|
|
-\3. Enable token verification plugin in your MUC component config section:
|
|
|
112
|
+\3. Enable room name token verification plugin in your MUC component config section:
|
|
113
|
113
|
|
|
114
|
114
|
```lua
|
|
115
|
115
|
Component "conference.jitmeet.example.com" "muc"
|