fix(accounts): enforce per-property scope restrictions via API - #60348
Open
miaulalala wants to merge 2 commits into
Open
fix(accounts): enforce per-property scope restrictions via API#60348miaulalala wants to merge 2 commits into
miaulalala wants to merge 2 commits into
Conversation
miaulalala
requested review from
ArtificialOwl,
come-nc,
leftybournes and
salmart-dev
and removed request for
a team
May 13, 2026 12:32
miaulalala
added
bug
3. to review
Contributor
Author
|
/backport to stable33 |
Contributor
Author
|
/backport to stable32 |
come-nc
requested changes
May 19, 2026
come-nc
approved these changes
May 26, 2026
come-nc
left a comment
come-nc
left a comment
Contributor
There was a problem hiding this comment.
Is federation of account info always going through the lookup server 🤔
miaulalala
force-pushed
the
fix/59225-profile-scope-api-bypass
branch
from
May 26, 2026 17:08
e9fcdde to
b4dbff6
Compare
Adds `UNPUBLISHED_PROPERTIES` to `IAccountManager` for profile fields that must never be federated or published to the global lookup server (biography, birthdate, headline, organisation, role), matching the frontend's `UNPUBLISHED_READABLE_PROPERTIES` constant. Enforces two new constraints in `testPropertyScope`: - `UNPUBLISHED_PROPERTIES` may not use `SCOPE_FEDERATED` or `SCOPE_PUBLISHED`, even when set via the API. - `SCOPE_PUBLISHED` is rejected for all properties unless the admin has enabled lookup server upload (`files_sharing.lookupServerUploadEnabled`). Previously the `PUT /ocs/v2.php/cloud/users/<uid>` endpoint accepted any valid scope value regardless of these restrictions, allowing users to bypass the visibility limits enforced by the frontend UI. Fixes #59225 Signed-off-by: Anna Larch <anna@nextcloud.com> AI-Assisted-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…tPropertyScope and fix @SInCE - Remove the always-true $throwOnData parameter from testPropertyScope; the dead else-branches (setScope(LOCAL)) are dropped, all paths now throw directly - Fix @SInCE annotation on UNPUBLISHED_PROPERTIES to 34.0.0 AI-Assisted-By: Claude Sonnet 4.6 <noreply@anthropic.com>
miaulalala
force-pushed
the
fix/59225-profile-scope-api-bypass
branch
from
June 24, 2026 11:31
b4dbff6 to
ec8d8fe
Compare
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #59225 — the
PUT /ocs/v2.php/cloud/users/<uid>API accepted any valid scope value for any profile property, allowing users to bypass the visibility restrictions enforced by the frontend UI (e.g. settingwebsiteScope=v2-publishedon an instance where the admin has disabled lookup server upload).IAccountManager::UNPUBLISHED_PROPERTIESconstant listing the profile fields that must never be federated or published (biography, birthdate, headline, organisation, role) — mirrors the frontend'sUNPUBLISHED_READABLE_PROPERTIEStestPropertyScopenow rejectsSCOPE_FEDERATED/SCOPE_PUBLISHEDfor those propertiestestPropertyScopenow rejectsSCOPE_PUBLISHEDfor all properties unless the admin has enabled lookup server upload (files_sharing.lookupServerUploadEnabled)Test plan
NOCOVERAGE=1 ./autotest.sh sqlite tests/lib/Accounts/AccountManagerTest.php— all 63 tests pass including 3 new onesPUT /ocs/v2.php/cloud/users/<uid>withbiographyScope=v2-federated→ expect HTTP 400Invalid scopePUT /ocs/v2.php/cloud/users/<uid>withwebsiteScope=v2-publishedon an instance with lookup server upload disabled → expect HTTP 400Invalid scope🤖 Generated with Claude Code