Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating a public upload share works with reduced permissions when allow public upload is off #31698

Closed
phil-davis opened this issue Jun 8, 2018 · 3 comments
Assignees

Comments

@phil-davis
Copy link
Contributor

phil-davis commented Jun 8, 2018

  1. Disable shareapi_allow_public_upload
  2. Create a share with permissions that include public upload (e.g. permissions = 31)
    Actual behavior:
  • the share is created but has less permissions - no public upload
  1. Enable shareapi_allow_public_upload
  2. Try to upload to the share as public - it does not work

Scenario is:
https://github.com/owncloud/core/blob/master/tests/acceptance/features/apiSharing-v1/uploadToShare.feature#L244

Expected behavior:
either:
a) at step 2 there should be an error response (4nn code) and the share is not created - because "the system" cannot create the share exactly as requested.

or

b) at step 2 the share is created with all permissions, including public upload. So it is "ready" to allow public upload if the system-wide setting shareapi_allow_public_upload is enabled in future.

Take your pick.

Note that if there are current shares with public upload permissions, and shareapi_allow_public_upload is disabled, then those shares "sit there" still and are just non-functional (good). If shareapi_allow_public_upload is later enabled, then those shares "come to life" again.

For that reason, I am inclined to behavior (b) - that you can disable front-end behavior like shareapi_allow_public_upload but still setup shares. Then when you are ready you can enable the front-end behavior and "the system comes to life".

@phil-davis
Copy link
Contributor Author

If someone defines what the behavior should be, we can easily add or modify acceptance test scenarios to suit.

@ownclouders
Copy link
Contributor

GitMate.io thinks possibly related issues are #18110 (upload in public shared folder creates errors ), #1367 ("Create" permission hidden when folder is first shared), #20839 (Sharing a file allows you to set create permissions), #22739 (Sharing permission issue), and #17486 (Allow folder creation in public share).

@ownclouders
Copy link
Contributor

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 7 days. Feel free to reopen this issue if you deem it appropriate.

(This is an automated comment from GitMate.io.)

@phil-davis phil-davis reopened this Jul 17, 2018
@phil-davis phil-davis removed their assignment Sep 4, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Oct 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants