Shared link password protection

[turbotorsten]

I just fired up an installation for testing and I believe the direction of this project looks really promising.

Whiile looking around the UI, it seems that password protection for shared links is enforced by default. Is this related to DSGVO compliance, and can it be disabled?

[rhafer]

Setting OC_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD=false should disable the requirement.

[micbar]

@ScharfViktor Can you try to reproduce?

[ScharfViktor]

I've appended the mentioned line with variable at the end of .env file and start the service. Then create a document, create a public link, change permissions to "Can edit" and get a password request for a link.

this is correct behavior

you have two envs (see here https://github.com/opencloud-eu/opencloud-compose/blob/main/docker-compose.yml#L48-L49)

if you set OC_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD=false and OC_SHARING_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD=true(set by default) you can create a link without password only for view permission.

please set
OC_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD=false and OC_SHARING_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD=false
if you want to disable password protection for all permissions

[mixeme]

Yes, it helps. Thank you! I think a mention of the second variable is missing in the documentation.
However, it works correctly only with the rolling image. When it will be in the stable branch?
With stable image, a link opens document only for viewing.

[ScharfViktor]

I think a mention of the second variable is missing in the documentation.

it's here https://docs.opencloud.eu/docs/dev/server/services/frontend/information#password-enforcement-for-writeable-public-links

However, it works correctly only with the rolling image

no, I tested it on 4.0.1 stable - works fine

and public can open both links (view or edit permisions)

[mixeme]

it's here https://docs.opencloud.eu/docs/dev/server/services/frontend/information#password-enforcement-for-writeable-public-links

This is a developer section of the documentation. Not for administrators.

I tested it on 4.0.1 stable - works fine

I had 4.0.0 version. After update to 4.0.1 stable, it works fine. Thank you!