nextcloud / nextcloud/server

[Bug]: Contacts addressbooks and Calendars can't be controlled for being reshared or not

Open
#37,964 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement feature: caldav feature: carddav feature: sharing
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

⚠️ This issue respects the following points: ⚠️
  • This is a bug, not a question or a configuration/webserver/proxy issue.
  • This issue is not already reported on Github (I've searched it).
  • Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
  • Nextcloud Server is running on 64bit capable CPU, PHP and OS.
  • I agree to follow Nextcloud's Code of Conduct.
Bug description

When a user shares an addressbook (Contacts) or a calendar, can not control if destination users are allowed to reshare the resource.

Steps to reproduce
  1. Configure server to allow users to reshare resources + Not resharing by default
  2. Go to configure my calendar, share to another user. Go to configure my contacts addressbook, share to another user.
  3. Login as the other user. Go to accessed calendar; I can reshare it. Go to accessed addressbook; I can reshare it.
Expected behavior
  1. On sharing callendars or addressbooks, there should be an option to allow or disallow resharing.
  2. User who receives shares, should not be allowed to reshare them if not selected as described.
Installation method

Community Web installer on a VPS or web space

Nextcloud Server version

25

Operating system

Debian/Ubuntu

PHP engine version

PHP 7.4

Web server

Apache (supported)

Database engine version

MariaDB

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?
  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other
Configuration report

No response

List of activated Apps
Enabled:
  - activity: 2.17.0
  - breezedark: 25.0.2
  - bruteforcesettings: 2.5.0
  - calendar: 4.3.3
  - calendar_resource_management: 0.3.1
  - circles: 25.0.0
  - cloud_federation_api: 1.8.0
  - comments: 1.15.0
  - contacts: 5.2.0
  - contactsinteraction: 1.6.0
  - data_request: 1.12.0
  - dav: 1.24.0
  - external: 5.0.2
  - federatedfilesharing: 1.15.0
  - federation: 1.15.0
  - files: 1.20.1
  - files_ebookreader: 0.0.1
  - files_external: 1.17.0
  - files_mindmap: 0.0.27
  - files_rightclick: 1.4.0
  - files_sharing: 1.17.0
  - files_trashbin: 1.15.0
  - files_versions: 1.18.0
  - firstrunwizard: 2.14.0
  - group_default_quota: 0.1.6
  - groupfolders: 13.1.2
  - groupquota: 0.1.10
  - impersonate: 1.12.0
  - logreader: 2.10.0
  - lookup_server_connector: 1.13.0
  - metadata: 0.18.0
  - notifications: 2.13.1
  - oauth2: 1.13.0
  - password_policy: 1.15.0
  - privacy: 1.9.0
  - provisioning_api: 1.15.0
  - quota_warning: 1.16.0
  - recommendations: 1.4.0
  - related_resources: 1.0.4
  - richdocumentscode: 22.5.1301
  - serverinfo: 1.15.0
  - settings: 1.7.0
  - sharebymail: 1.15.0
  - systemtags: 1.15.0
  - text: 3.6.0
  - theming: 2.0.1
  - theming_customcss: 1.13.0
  - twofactor_backupcodes: 1.14.0
  - updatenotification: 1.15.0
  - user_status: 1.5.0
  - viewer: 1.9.0
  - workflowengine: 2.7.0
Disabled:
  - admin_audit
  - audioplayer: 3.3.1
  - dashboard: 7.3.0
  - encryption
  - extract: 1.3.5
  - files_3d: 0.5.0
  - files_pdfviewer: 2.4.0
  - mail: 2.2.6
  - nextcloud_announcements: 1.12.0
  - photos: 1.5.0
  - richdocuments: 7.1.3
  - socialsharing_diaspora: 2.5.0
  - socialsharing_email: 2.5.0
  - spreed: 15.0.5
  - support: 1.6.0
  - survey_client: 1.11.0
  - suspicious_login
  - twofactor_totp
  - user_ldap
  - weather_status: 1.3.0
Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

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

Start by tracing the sharing behavior in the calendar and contacts apps using the listed reproduction steps. Done means sharing either resource offers an allow-or-disallow-resharing choice and a recipient cannot reshare it when disallowed.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
authorization, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.