nextcloud / nextcloud/spreed

Limit to groups in federated target server breaks federation

Open
#12,429 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature: federation 🌐 feature: frontend 🖌️ feature: settings ⚙️ good first issue
Dominant language
PHP
Stars
2.2k
Forks
587
Avg merge
18h 27m
Merged PRs (30d)
333

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Steps to reproduce

  1. Admin of nc2 enables federation and sets the following settings:
    image
    user2 is both in groups admin and general.
  2. user1@nc1 invites user2@nc2 into a federated conversation
Expected behaviour

Successful creation of a federated conversation. Limit to groups should limit the possibility to invite, not to be invited and in any case user2 is part of the groups allowed to use federation.

Removing all groups from "Limit to groups" prevents the issue.

Actual behaviour

Conversation is not created or invite fails.
nc2 logs:

Received a federation invite for user that is not allowed to use Talk Federation

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified. Reproduce the invite between nc1 and nc2 with a user in both an allowed and another group, then trace the federation authorization handling that produces the logged rejection. Done means an allowed user can be invited and the federated conversation is created while the group limit still restricts outgoing invitations.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.