Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(federation): Propagate permission changes to federated servers #13092

Merged
merged 3 commits into from
Aug 22, 2024

Conversation

nickvergessen
Copy link
Member

@nickvergessen nickvergessen commented Aug 22, 2024

☑️ Resolves

🛠️ API Checklist

Modifications to original PR:

  • 1 commit: Only propagate to the affected participant and extended the test with something that failed before and now passes
  • 2 commit: Dropped as the permissions is now "simple" like all other room properties as the chained and other parts got dropped with fix(conversations): Remove call-permissions #13086
  • 3 commit: Removed references to call permissions
  • 4 commit: Removed references to call permissions

🏁 Checklist

  • ⛑️ Tests (unit and/or integration) are included or not possible
  • 📘 API documentation in docs/ has been updated or is not required
  • 🔖 Capability is added or not needed

@nickvergessen nickvergessen added this to the 🖤 Next Major (31) milestone Aug 22, 2024
@nickvergessen nickvergessen requested a review from danxuliu August 22, 2024 12:31
@nickvergessen nickvergessen self-assigned this Aug 22, 2024
@nickvergessen nickvergessen changed the title Bugfix/12953/propagate permissions fix(federation): Propagate permission changes to federated servers Aug 22, 2024
Copy link
Member

@danxuliu danxuliu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will rebase and also fix the problem from my comment once #13086 is merged.

Edit: force pushed with [skip-ci] in the last commit in case the base PR is merged while I am way.

tests/integration/features/federation/permissions.feature Outdated Show resolved Hide resolved
@danxuliu danxuliu force-pushed the bugfix/12953/propagate-permissions branch from 3c151fe to 4fa4be2 Compare August 22, 2024 15:18
The frontend gets the permission for the current participant from the
room data (as guest users can not get it from the participant list).
However, permission changes were not propagated to federated server, so
the frontend of federated users always assumed that the user had the
default permissions.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
When a participant does not have custom permissions the permissions are
got from the conversation, so they need to be propagated as well
to the federated servers to correctly calculate the participant
permissions.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Besides propagating the permissions to federated servers when modified
the existing permissions need to be set when creating the federated
conversation (or if a federated user is added again to the conversation
when all the previous federated users left it already).

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
@nickvergessen nickvergessen force-pushed the bugfix/12953/propagate-permissions branch from 4fa4be2 to 02aedb1 Compare August 22, 2024 16:23
@nickvergessen
Copy link
Member Author

/backport to stable30

@nickvergessen nickvergessen merged commit 06ee86c into main Aug 22, 2024
69 checks passed
@nickvergessen nickvergessen deleted the bugfix/12953/propagate-permissions branch August 22, 2024 17:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review bug feature: api 🛠️ OCS API for conversations, chats and participants feature: federation 🌐
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Federated users are not aware of changed permissions
2 participants