We are using JaaS and a local/self-hosted version of Jitsi.
At our JaaS deployment, we add the following context at our JWT token payload:
'context' => [ 'user' => [ 'moderator' => $USER_IS_MODERATOR ? "true" : "false", 'email' => $USER_EMAIL, 'name' => $USER_NAME, 'avatar' => $USER_AVATAR_URL, 'id' => $USER_ID ], 'features' => [ 'recording' => $RECORDING_IS_ENABLED ? "true" : "false", 'livestreaming' => $LIVESTREAMING_IS_ENABLED ? "true" : "false", 'transcription' => $TRANSCRIPTION_IS_ENABLED ? "true" : "false", 'outbound-call' => $OUTBOUND_IS_ENABLED ? "true" : "false" ] ]
If we try the same setup for our local jitsi deployment, it does’nt work. The name value is fully functional, but the moderator rights as well as all the features (recording, livestreaming) are not recognized.
We are only using the jitsi-meet-token plugin. Is there any additional plugin we need to install to get this functionality?