* [Galene] Heads up: slight change to the format of tokens
@ 2024-05-08 15:13 Juliusz Chroboczek
0 siblings, 0 replies; only message in thread
From: Juliusz Chroboczek @ 2024-05-08 15:13 UTC (permalink / raw)
To: galene
Hi,
I've just implemented the commands /shutup and /unshutup, which make it
possible to prevent a client from sending chat messages. It's the second
time that this
Sending messages is now governed by an explicit permission (the right to
send messages used to be implicitly granted). This means that:
- if you're using the "new" configuration format, you should use
"message" instead of "observe" if you wish to grant a user the
permission to send messages but not to participate with video and
audio; "observe" no longer has the right to send chat messages;
- if you're using the old (0.8) configuration format, nothing changes;
- if you're using galene-ldap, you need to upgrade to a version dated
2024-05-08 or later;
- if you're generating stateless tokens in your own software, you need
to add the "message" value to the "permissions" field in addition to
the "present" value.
As far as stateful tokens are concerned, Galene master transparently adds
the "message" permission when loading tokens from disk; the effect is that
it's not currently possible to generate a token without the "message"
permission (or, more accurately, it's possible to generate such a token,
but the "message" permission will be added as soon as the token is
reloaded from disk). I intend to remove this hack sometime in late 2024.
-- Juliusz
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2024-05-08 15:13 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-05-08 15:13 [Galene] Heads up: slight change to the format of tokens Juliusz Chroboczek
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox