Update room permissions leads to conflicts #159
Comments
guusdk
added a commit
to guusdk/openfire-restAPI-plugin
that referenced
this issue
Nov 1, 2022
guusdk
added a commit
to guusdk/openfire-restAPI-plugin
that referenced
this issue
Nov 1, 2022
Issues pop up when an attempt is ade to affiliate a JID more than once, especially when that JID is also an owner. Affiliating such a JID as something else will remove the ownership affiliation. This can trigger an issue where the room has no owners. This commit introduces a check to verify that the inbound request does not define multiple affiliations for the same JID. It also reworks the way in which affiliations are applied.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a room's user permissions are being updated, conflicts arise (but are not logged).
It appears that the implementation first removes all permissions, to then update them to the desired configuration.
This intermediate step briefly removes all owners, which is forbidden (a room must always have an owner), causing a conflict.
The text was updated successfully, but these errors were encountered: