⚠️ This issue respects the following points: ⚠️
Bug description
Actual behavior:
The UI fails to apply the tag. The browser console shows a 403 Forbidden error triggered by the WebDAV PROPPATCH request. It appears the WebDAV subsystem restricts tag assignment strictly to the user who originally created the tag, ignoring the public status in the database.
Steps to reproduce
- Log in as User A (e.g., Admin).
- Go to Settings -> Collaborative tags. Create a new tag (e.g., "Ready for dispatch") and set its access level to Public (Shared/Visible).
- Log out and log in as User B (standard user).
- Select any file owned by User B (even a newly created one) and attempt to assign the public tag from the dropdown list.
- The UI shows an error: "Failed to apply tags".
(Note: The issue is completely symmetrical. If User B creates the public tag, User B can assign it, but Admin gets a 403 error).
Expected behavior
Since the tag is configured as "Public", any user with write access to the file should be able to assign the tag successfully.
Nextcloud Server version
34
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.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?
No response
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
Errors in browser console:
Failed to load resource: the server responded with a status of 403 (Forbidden)
xhr-request.js:128 PROPPATCH https://cloud.domain.com/remote.php/dav/systemtags/6/files 403 (Forbidden)
SystemTagPicker.vue:538 [ERROR] systemtags: Failed to apply tags {app: 'systemtags', uid: 'bingo', level: 3, error: Error: Invalid response: 403 Forbidden}
Bug description
Actual behavior:
The UI fails to apply the tag. The browser console shows a 403 Forbidden error triggered by the WebDAV PROPPATCH request. It appears the WebDAV subsystem restricts tag assignment strictly to the user who originally created the tag, ignoring the public status in the database.
Steps to reproduce
(Note: The issue is completely symmetrical. If User B creates the public tag, User B can assign it, but Admin gets a 403 error).
Expected behavior
Since the tag is configured as "Public", any user with write access to the file should be able to assign the tag successfully.
Nextcloud Server version
34
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.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?
No response
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
Errors in browser console:
Failed to load resource: the server responded with a status of 403 (Forbidden)
xhr-request.js:128 PROPPATCH https://cloud.domain.com/remote.php/dav/systemtags/6/files 403 (Forbidden)
SystemTagPicker.vue:538 [ERROR] systemtags: Failed to apply tags {app: 'systemtags', uid: 'bingo', level: 3, error: Error: Invalid response: 403 Forbidden}