You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once I start recording using jibri, the system automatically gives moderator role to random participant ! (Sometimes)
Even I have disabled auto owner!
And tried to enable guest and join with jwt
(To prevent upgrading anyone to be moderator and start/stop recording and same problem) but still upgrading even guests !!
I tried to see logs of jibri,jicofo,prosody once I start recording but nothing related to upgrading anyone!
Note:
Iam using token_affiliation Plugin to handle roles
And I see that all users start the meeting with moderation access whatever I put inside token, then after a part of second it downgrade to specific role successfully
I have 5 days searching but still same problem 😔 I need help please
The text was updated successfully, but these errors were encountered:
and this is my env file iam using kubernates and just single env file shared with all pods https://codeshare.io/64Xynk
when i try to make meeting with (for example) 5 persons and try to record suddenly one of the participants became a moderator without my permission (happened from time to time) @saghul
Once I start recording using jibri, the system automatically gives moderator role to random participant ! (Sometimes)
Even I have disabled auto owner!
And tried to enable guest and join with jwt
(To prevent upgrading anyone to be moderator and start/stop recording and same problem) but still upgrading even guests !!
I tried to see logs of jibri,jicofo,prosody once I start recording but nothing related to upgrading anyone!
Note:
Iam using token_affiliation Plugin to handle roles
And I see that all users start the meeting with moderation access whatever I put inside token, then after a part of second it downgrade to specific role successfully
I have 5 days searching but still same problem 😔 I need help please
The text was updated successfully, but these errors were encountered: