Features (such as recording, screen-sharing) are always disabled in UI if enableFeaturesBasedOnToken is enabled in config.js and if there is no user data in token's context.
Steps to reproduce:
enable token authentication in prosody
enable enableFeaturesBasedOnToken in config.js
create a token with some features (for example enable recording) but don't add user data into token's context
create a meeting as moderator, try to click start recording
Expected behavior:
Features should be enabled in UI if they are already set as true in token.
Actual behavior:
Features which are set in token are no effect on UI.
Server information:
ii jicofo 1.0-910-1
ii jitsi-meet 2.0.7577-1
ii jitsi-meet-prosody 1.0.6380-1
ii jitsi-meet-tokens 1.0.6380-1
ii jitsi-meet-turnserver 1.0.6380-1
ii jitsi-meet-web 1.0.6380-1
ii jitsi-meet-web-config 1.0.6380-1
ii prosody 0.11.9-2+deb11u2 amd64
Debian 11 Bullseye
Client information:
Debian 11 BullseyeChrome Version 104.0.5112.79
Additional information:
When there is a user data in token's context, everything works as expected
Description:
Features (such as recording, screen-sharing) are always disabled in UI if
enableFeaturesBasedOnToken
is enabled inconfig.js
and if there is no user data in token'scontext
.Steps to reproduce:
token
authentication inprosody
enableFeaturesBasedOnToken
inconfig.js
recording
) but don't adduser
data into token'scontext
moderator
, try to clickstart recording
Expected behavior:
Features should be enabled in UI if they are already set as
true
in token.Actual behavior:
Features which are set in token are no effect on UI.
Server information:
Debian 11 Bullseye
Client information:
Debian 11 Bullseye
Chrome Version 104.0.5112.79
Additional information:
When there is a
user
data in token'scontext
, everything works as expected