From 3f70914f10410e674994c06053900a0ee17eaff3 Mon Sep 17 00:00:00 2001 From: Sascha Wiswedel Date: Fri, 15 May 2020 10:25:16 +0200 Subject: [PATCH] Drawbacks of SAML auth on server-side encryption and 2nd hand auth Signed-off-by: Sascha Wiswedel --- admin_manual/configuration_files/encryption_details.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/admin_manual/configuration_files/encryption_details.rst b/admin_manual/configuration_files/encryption_details.rst index 6103074d9..7a87a2f94 100644 --- a/admin_manual/configuration_files/encryption_details.rst +++ b/admin_manual/configuration_files/encryption_details.rst @@ -38,6 +38,8 @@ Key type: user key While the user key encryption has been enabled by default in older versions of Nextcloud it now has to be enabled explicitly in newer versions including Nextcloud 16 by calling ``./occ encryption:disable-master-key``. With user key encryption enabled all users have their own user keys that are used to secure the files handled by Nextcloud. The user keys are protected by the user passwords. The advantage is that the server administrator is not able to decrypt user files without knowing any user password - unless the file is publicly shared or a recovery key is defined - but has the disadvantage that files are permanently lost if the users forget their user passwords - unless the files are (publicly) shared or a recovery key is defined. +.. note:: This method cannot be used with SAML authentication, because Nextcloud does not get a hold of any credentials whatsoever and therefore cannot use any users' passwords for encryption. + .. _file_type_public_key_file_label: File type: public key file