Error in Nextcloud 14 Beta 3 Missing "Enable recovery key" field in the admin settings

[ghost]

Getting this error after updating to NC 14 Beat 3 from NC 13

[nextcloud-bot]

GitMate.io thinks possibly related issues are #8283 (Missing "Enable recovery key" field in the admin settings), #10502 (Nextcloud 14 Beta 3), #10624 (Nextcloud 14 Beta 3 The "Referrer-Policy" HTTP header is not set to "no-referrer"), #10627 (Upgrade Nextcloud 14 : Copy error step 3 backup), and #10410 (Nextcloud 14 Beta 2).

[rullzer]

@nextcloud/encryption

[schiessle]

@andyxh what was the Nextcloud version you enabled encryption for the first time? Can you execute this query on your database and post the result: select * from oc_appconfig where appid="encryption";

[ghost]

@schiessle im sorry I dont remember the version i think it was 10 or 11

mysql> select * from oc_appconfig where appid="encryption";
+------------+----------------------+----------------------+
| appid | configkey | configvalue |
+------------+----------------------+----------------------+
| encryption | enabled | yes |
| encryption | encryptHomeStorage | 1 |
| encryption | installed_version | 2.1.0 |
| encryption | masterKeyId | master_0c89db0b |
| encryption | publicShareKeyId | pubShare_0c89db0b |
| encryption | recoveryAdminEnabled | 1 |
| encryption | recoveryKeyId | recoveryKey_0c89db0b |
| encryption | types | filesystem |
| encryption | useMasterKey | 0 |
+------------+----------------------+----------------------+
9 rows in set (0.00 sec)

[skjnldsv]

@schiessle does that ring a bell to you?
Iirc we decired to remove the password change if encryption was enabled.

server/settings/Controller/UsersController.php

Lines 170 to 174 in 2afd373

	/* ENCRYPTION CONFIG */
	$isEncryptionEnabled = $this->encryptionManager->isEnabled();
	$useMasterKey = $this->config->getAppValue('encryption', 'useMasterKey', true);
	// If masterKey enabled, then you can change password. This is to avoid data loss!
	$canChangePassword = ($isEncryptionEnabled && $useMasterKey) || $useMasterKey;

[schiessle]

yes, we removed it for Nextcloud 14. The reason was that it was only possible with the recovery key enabled. Which worked fine, but only for relatively small accounts because all files had to be re-encrypted. As this could took really long on larger accounts and often ended in timeouts we decided to remove it in the user management. Users can still change their password in the personal settings.

[ghost]

@schiessle So what happens to the message I keep getting? And admins are not longer about to change passwords for users ?? Also i have the recovery key enabled on NC 13 and im able to reset password via admin account but once i did the update to NC 14 i get that error??

…

Sent from my iPhone X On Aug 15, 2018, at 8:37 AM, Björn Schießle <notifications@github.com<mailto:notifications@github.com>> wrote: yes, we removed it for Nextcloud 14. The reason was that it was only possible with the recovery key enabled. Which worked fine, but only for relatively small accounts because all files had to be re-encrypted. As this could took really long on larger accounts and often ended in timeouts we decided to remove it in the user management. Users can still change their password in the personal settings. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#10630 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AXb4Q5SDZevl0ytfXAQc7KtAvidSc75_ks5uRCQvgaJpZM4V2VhZ>.

[schiessle]

So what happens to the message I keep getting? And admins are not longer about to change passwords for users ??

Yes, the user should change their password by their own. This way the private key can be updated without re-encrypting all files

[ghost]

@schiessle Okay, so what happens is the case that they dont remember it? Also, will this message keep coming up every time i go under users?

[schiessle]

@andyxh there will be a occ command to recover user files in the future: #10718

[ghost]

@schiessle That's awesome news! Is there going to be a way to take that message out? is very anoyying getting that error every time someone has to click on users.

[stone212]

@schiessle I run a server that does not have encryption but I still get this error and the password fields for users is blank. On NC13 (snap) I could change all users passwords.

[godfuture]

I had encryption enabled but never used to encrypt user homes. Short time after I disabled encryption, because I dont like it. Now I get this message, even I do not want to have encryption. What to do?