nextcloud / nextcloud/server

Admin setting to disable anonymous profile URLs

Open
#63,753 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

[!TIP]

Help move this idea forward
  • Use the 👍 reaction to show support for this feature.
  • Avoid commenting unless you have relevant information to add; unnecessary comments create noise for subscribers.
  • Subscribe to receive notifications about status changes and new comments.

Is your feature request related to a problem? Please describe.

The profile pages on /u/ are publicly available, see https://github.com/nextcloud/server/issues/32086 . Users are currently able to specify per field who may see it. This is error prone for me because I have a Nextcloud that shouldn't be visible to the outside.

Describe the solution you'd like

Add an admin setting to be able to disable anonymous access to the profile pages. Thus only logged in users (and guests) are allowed to see profiles.

Describe alternatives you've considered

Current workaround is completely disabling the profiles in the server config. But then, my users can't view each others profile.

Additional context

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 with the existing /u/ profile pages and the current server-config workaround that disables profiles. Trace how anonymous access and admin settings are handled; done means an administrator can disable anonymous profile access while logged-in users and guests can still view profiles.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.