Federated inherited circle members can't access shared resources from parent circle
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 177
- Forks
- 68
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 60
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.
Inherited members from federated remote team doesn't see shared resources despite mount entries being created.
Steps to reproduce
- setup federation environment with two Nextcloud instances (e.g.
nc_1+nc_2) - on
nc_1asbob:
- create
test_teamand check "Allow federated members" - add
johnfromnc_2(john@nc_2)
- on
nc_2asjohn:
- create
remote_team - add
alice
- on
nc_1, addremote_teamtotest_team:
occ circles:members:add --type 16 <test-team-id> <remote-team-id>@nc_2
- on
nc_1, as bob
- create
test_folderand share withtest_team
- on
nc_2asalice
- navigate to files > "All files"
- notice how
test_folderdoes not appear there, which is incorrect - note: entries are generated on
oc_circles_mountandoc_circles_mountpoint
Expected behaviour
when a remote circle (from another instance) is added as a member of a circle, members inherited from that remote circle should be able to access resources shared with the parent circle.
Actual behaviour
the resource does not appear for the inherited member (alice), even though entries are generated on oc_circles_mount and oc_circles_mountpoint.
Server configuration
Web server: Apache/Nginx
Database: MySQL/Maria/SQLite/PostgreSQL
PHP version: 8.5/8.4/8.3
Nextcloud version: Nextcloud 36.0.0 dev
List of activated apps
Enabled: - appstore: 3.0.0-dev.0 - circles: 36.0.0-dev.0 - cloud_federation_api: 3.0.0-dev.0 - comments: 3.0.0-dev.0 - contactsinteraction: 3.0.0-dev.0 - dashboard: 9.0.0-dev.0 - dav: 3.0.0-dev.0 - federatedfilesharing: 3.0.0-dev.0 - federation: 3.0.0-dev.0 - files: 4.0.0-dev.0 - files_pdfviewer: 8.0.0-dev.0 - files_reminders: 3.0.0-dev.0 - files_sharing: 3.0.0-dev.0 - files_trashbin: 3.0.0-dev.0 - files_versions: 3.0.0-dev.0 - lookup_server_connector: 3.0.0-dev.0 - oauth2: 3.0.0-dev.0 - profile: 3.0.0-dev.0 - provisioning_api: 3.0.0-dev.0 - recommendations: 8.0.0-dev.0 - settings: 3.0.0-dev.0 - sharebymail: 3.0.0-dev.0 - sharing: 2.0.0-dev.1 - systemtags: 3.0.0-dev.0 - text: 9.0.0-dev.0 - theming: 4.0.0-dev.0 - twofactor_backupcodes: 3.0.0-dev.0 - updatenotification: 3.0.0-dev.0 - user_status: 3.0.0-dev.0 - viewer: 8.0.0-dev.0 - weather_status: 3.0.0-dev.0 - webhook_listeners: 3.0.0-dev.0 - workflowengine: 4.0.0-dev.0 Disabled: - admin_audit: 3.0.0-dev.0 - contacts: 8.8.0-dev.0 - encryption: 4.0.0-dev.0 - files_external: 3.0.0-dev.0 - globalsiteselector: 2.7.3 - groupfolders: 23.0.0-dev.3 - hmr_enabler: 1.4.0-dev.0 - profiler: 6.0.0-dev.0 - testing: 3.0.0-dev.0 - user_ldap: 3.0.0-dev.0 - user_oidc: 8.11.0 ``` If you have access to your command line run e.g.: sudo -u www-data php occ app:list from within your Nextcloud installation folder ```Nextcloud configuration
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
Browser
Browser name: Firefox/Chrome/Safari/…
Browser version: 124/125/…
Operating system: Windows/Ubuntu/Mac/…
Browser log
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the two-instance federation setup and the occ circles:members:add --type 16 entry point. Inspect the generated oc_circles_mount and oc_circles_mountpoint entries while checking why the inherited member cannot see test_folder. Done means alice can access the resource shared with test_team from the parent instance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authorization, backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100