LiveKit Community

Can you say more about `it can reconnect again and it can publish again` ? how is the participant reconnecting?

if you are connecting again, you'd need to ensure the user's token is updated to remove `canPublish`. If livekit automatically reconnects, it *should not* give that user publish permissions. we have checks against that case.

Once i mute the publisher remotely by setting `canPublish` to false - the publisher get’s muted successfully but then he/she click disconnect and connect again and it can publish again. The token is not updated in LiveKit for some reason and this is the exception it throws when this is happening(updatingParticipant)

LiveKit does not control the token.. As you were saying, when the user clicks "disconnect" and then "connect", your application is passing in a token to the `connect` function in LiveKit. That token contains publish permissions. Am I correct in understanding that?

Yes it does, but what if the user capture the old token with publish permissions and connect again with it

yes, that's what we'd recommend. your webpage should refresh its token *after* the user presses the connect button.

I did another fix thought but the interesting part from my POV is that livekit is updating the claims but is that only in runtime or…? Also what about the error when muting is it expected behaviour(i attached logs above)

LiveKit updates the claims for its internal reconnect token (should it need to resume for connectivity changes). It cannot control the token that you are going to pass into it

Got it! Thanks for your time and great work!