external storage new auth mechanisms

This commit is contained in:
Carla Schroder 2016-03-01 09:35:48 -08:00
parent 1506de7c05
commit ae8733fb69
6 changed files with 11 additions and 12 deletions

View File

@ -25,11 +25,12 @@ Password-based Mechanisms
The **Username and password** mechanism requires a manually-defined username and
password. These get passed directly to the backend.
The **Session credentials** mechanism uses the ownCloud login 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 drawback is that
sharing is disabled when this mechanism is in use, as ownCloud has no access
to the storage credentials and so other users cannot use it.
The **Log-in credentials, save in session** mechanism uses the ownCloud login
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
ownCloud has no access to the storage credentials, and background file scanning
does not work.
Public-key Mechanisms
---------------------

Binary file not shown.

Before

Width:  |  Height:  |  Size: 20 KiB

After

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 10 KiB

View File

@ -11,7 +11,7 @@ Enabling External Storage Support
The External storage support application is enabled on your Apps page.
.. figure:: external_storage/images/enable_app.png
.. figure:: external_storage/images/enable-app.png
:alt: Enable external storage on your Apps page.
Storage Configuration
@ -29,12 +29,10 @@ authentication mechanisms; some specific to the backend, others are more
generic. See :doc:`external_storage/auth_mechanisms` for more detailed
information.
When you select an authentication mechanism, the configuration
fields change as appropriate for the mechanism. Some backends are not yet
migrated to
the new authentication mechanism system, and are displayed with a mechanism
of **Built-in**. The SFTP backend, to give an example, supports both
password-based authentication and public key authentication.
When you select an authentication mechanism, the configuration fields change as
appropriate for the mechanism. The SFTP backend, for one example, supports
**username and password**, **Log-in credentials, save in session**, and **RSA
public key**.
.. figure:: external_storage/images/auth_mechanism.png
:alt: An SFTP configuration example.

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB