From a90410f0df291b4ba059bb2ed67dcad4f233ff73 Mon Sep 17 00:00:00 2001 From: Dirk Sarpe Date: Fri, 21 Feb 2020 16:02:28 +0100 Subject: [PATCH] Warn that synchronisation clients can not access save in session shares see https://github.com/nextcloud/server/issues/19561 Signed-off-by: Dirk Sarpe --- .../external_storage/auth_mechanisms.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/admin_manual/configuration_files/external_storage/auth_mechanisms.rst b/admin_manual/configuration_files/external_storage/auth_mechanisms.rst index 5463483bd..2439574a1 100644 --- a/admin_manual/configuration_files/external_storage/auth_mechanisms.rst +++ b/admin_manual/configuration_files/external_storage/auth_mechanisms.rst @@ -35,9 +35,10 @@ credentials of the user to connect to the storage. These are not stored anywhere on the server, but rather in the user session, giving increased security. The drawbacks are that sharing is disabled when this mechanism is in use, as Nextcloud has no access to the storage credentials, and background file scanning -does not work. Other services that might request the file through a different -request like Collabora Online or OnlyOffice will also not be able to open files -in that case. +does not work. Desktop and mobile clients that use tokens to authenticate can +not access those shares. Other services that might request the file through +a different request like Collabora Online or OnlyOffice will also not be able to +open files in that case. The **Log-in credentials, save in database** mechanism uses the Nextcloud login credentials of the user to connect to the storage. These are stored in the