nextcloud / nextcloud/server

Howto use file_accesscontrol AND public filesharing together?

Open
#38,182 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement feature: sharing feature: workflows
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

Hello
We have several directories where we block access with hidden tags for certain users with file_accesscontrol by group-memberships.

Problem:
this works well as long as we access the files normaly as nextcloud-users. But as soon as we want to share a file with a public link, the link cannot be accessed, as the connecting person is not member of the internal group for which access is.

For now we had a workaround to add several conditions on all our file-access-rules like the followings:

"url" not like "/^./public.php/./"
"url" not like "/^./apps/richdocuments/./"
"url" not like "/^./apps/files_sharing/./"
"url" not like "/^./s/.{15}./"

this workaround gets quite confusing, because we have to set all those conditions on every blocking-rule.

So we are looking fo a better solution to handle this situation. I think it could work if there was a possibility to create not only "blocking" rules but also "allow" rules. But this functionality is not available...isn't it?

Does someone have an idea how to better solve this problem when sharing files or folders that are blocked with file_accescontrol?

Thanks for your help
René

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

The issue names file_accesscontrol and public file-sharing routes, including public.php, richdocuments, files_sharing, and /s/ links. Start by tracing how access rules are applied to public links and document the desired interaction between blocking and allow rules. Done means a clear, maintainable behavior for sharing blocked files without repeating URL conditions.

Written by the indexing model from the issue text.

Assessment

Domain
authorization, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.