Skip to content

Commit a410395

Browse files
committed
fix: Re-order sections related to encryption
Signed-off-by: Côme Chilliet <[email protected]>
1 parent 9223f15 commit a410395

File tree

1 file changed

+57
-56
lines changed

1 file changed

+57
-56
lines changed

Diff for: admin_manual/configuration_files/encryption_configuration.rst

+57-56
Original file line numberDiff line numberDiff line change
@@ -131,61 +131,6 @@ Encryption settings can be configured in the mount options for an external
131131
storage mount, see :ref:`external_storage_mount_options_label`
132132
(:doc:`external_storage_configuration_gui`)
133133

134-
Using user keys
135-
---------------
136-
137-
If you disabled master key and are using user keys instead, mind the following information:
138-
139-
Sharing encrypted files
140-
^^^^^^^^^^^^^^^^^^^^^^^
141-
142-
After encryption is enabled your users must also log out and log back in to
143-
generate their personal encryption keys. They will see a yellow warning banner
144-
that says "Encryption App is enabled but your keys are not initialized, please
145-
log-out and log-in again."
146-
147-
Share owners may need to re-share files after encryption is enabled; users
148-
trying to access the share will see a message advising them to ask the share
149-
owner to re-share the file with them. For individual shares, un-share and
150-
re-share the file. For group shares, share with any individuals who can't access
151-
the share. This updates the encryption, and then the share owner can remove the
152-
individual shares.
153-
154-
.. figure:: images/encryption9.png
155-
156-
.. _enable-file-recovery-key:
157-
158-
Enabling users file recovery keys
159-
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
160-
161-
If you lose your Nextcloud password, then you lose access to your encrypted
162-
files. If one of your users loses their Nextcloud password their files are
163-
unrecoverable. You cannot reset their password in the normal way; you'll see a
164-
yellow banner warning "Please provide an admin recovery password, otherwise all
165-
user data will be lost".
166-
167-
To avoid all this, create a Recovery Key. Go to the Encryption section of your
168-
Admin page and set a recovery key password.
169-
170-
.. figure:: images/encryption10.png
171-
172-
Then your users have the option of enabling password recovery on their Personal
173-
pages. If they do not do this, then the Recovery Key won't work for them.
174-
175-
.. figure:: images/encryption7.png
176-
177-
For users who have enabled password recovery, give them a new password and
178-
recover access to their encrypted files by supplying the Recovery Key on the
179-
Users page.
180-
181-
.. figure:: images/encryption8.png
182-
183-
You may change your Recovery Key password.
184-
185-
.. figure:: images/encryption12.png
186-
187-
Please check the various key types in detail `here <encryption_details.html>`_
188-
189134
.. _occ_encryption_label:
190135

191136
occ encryption commands
@@ -320,8 +265,64 @@ filenames or folder structures. These files are never encrypted:
320265
There may be other files that are not encrypted; only files that are exposed to
321266
third-party storage providers are guaranteed to be encrypted.
322267

268+
269+
Using user keys
270+
---------------
271+
272+
If you disabled master key and are using user keys instead, mind the following information:
273+
274+
Sharing encrypted files
275+
^^^^^^^^^^^^^^^^^^^^^^^
276+
277+
After encryption is enabled your users must also log out and log back in to
278+
generate their personal encryption keys. They will see a yellow warning banner
279+
that says "Encryption App is enabled but your keys are not initialized, please
280+
log-out and log-in again."
281+
282+
Share owners may need to re-share files after encryption is enabled; users
283+
trying to access the share will see a message advising them to ask the share
284+
owner to re-share the file with them. For individual shares, un-share and
285+
re-share the file. For group shares, share with any individuals who can't access
286+
the share. This updates the encryption, and then the share owner can remove the
287+
individual shares.
288+
289+
.. figure:: images/encryption9.png
290+
291+
.. _enable-file-recovery-key:
292+
293+
Enabling users file recovery keys
294+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
295+
296+
If you lose your Nextcloud password, then you lose access to your encrypted
297+
files. If one of your users loses their Nextcloud password their files are
298+
unrecoverable. You cannot reset their password in the normal way; you'll see a
299+
yellow banner warning "Please provide an admin recovery password, otherwise all
300+
user data will be lost".
301+
302+
To avoid all this, create a Recovery Key. Go to the Encryption section of your
303+
Admin page and set a recovery key password.
304+
305+
.. figure:: images/encryption10.png
306+
307+
Then your users have the option of enabling password recovery on their Personal
308+
pages. If they do not do this, then the Recovery Key won't work for them.
309+
310+
.. figure:: images/encryption7.png
311+
312+
For users who have enabled password recovery, give them a new password and
313+
recover access to their encrypted files by supplying the Recovery Key on the
314+
Users page.
315+
316+
.. figure:: images/encryption8.png
317+
318+
You may change your Recovery Key password.
319+
320+
.. figure:: images/encryption12.png
321+
322+
Please check the various key types in detail `here <encryption_details.html>`_
323+
323324
LDAP and other external user back-ends
324-
--------------------------------------
325+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
325326

326327
If you use an external user back-end, such as an LDAP or Samba server, and you
327328
change a user's password on the back-end, the user will be prompted to change

0 commit comments

Comments
 (0)