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

Documentation/58141 Document Nextcloud GroupFolder encryption activation command #16870

Conversation

dominic-braeunlein
Copy link
Contributor

Ticket

#58141

What are you trying to accomplish?

This PR adds a description for Nextcloud admins that face the problem that some files are not encrypted on Nextcloud

@dominic-braeunlein dominic-braeunlein changed the base branch from dev to release/14.6 October 1, 2024 11:59
@dominic-braeunlein dominic-braeunlein force-pushed the documentation/58141-document-nextcloud-groupfolder-encryption-activation-command branch from c09961a to b16eb3d Compare October 1, 2024 12:03
Copy link
Member

@Kharonus Kharonus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

But it raises the question, if actually our integration should be able to detect server-side encryption automatically and set this configuration. On the other hand, configuring 3rd party apps generally is a bad idea from any plugin.

@dominic-braeunlein
Copy link
Contributor Author

if actually our integration should be able to detect server-side encryption automatically and set this configuration.

We are investigating on a detection of the encryption and displaying a warning in the settings
https://community.openproject.org/projects/nextcloud-integration/work_packages/57970/activity#activity-10

@dominic-braeunlein dominic-braeunlein merged commit f26e0e5 into release/14.6 Oct 2, 2024
7 checks passed
@dominic-braeunlein dominic-braeunlein deleted the documentation/58141-document-nextcloud-groupfolder-encryption-activation-command branch October 2, 2024 07:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants