https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33934
David Nind <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Text to go in the| |This fixes an issue that release notes| |can cause upgrades to Koha | |23.05 to fail with an error | |message that includes 'No | |encryption_key in | |koha-conf.xml'. It also | |requires the configuration | |entry in the instance | |koha-conf.xml to be | |something other than | |__ENCRYPTION_KEY__, for | |example: | |<encryption_key>mY$ecret%ey | |</encryption_key>. (It is | |recommended that the key is | |generated using pwgen 32) --- Comment #4 from David Nind <[email protected]> --- Testing notes (using KTD): 1. After removing the <encryption_key> entry in /etc/koha/sites/kohadev/koha-conf.xml and restarting, there is: - a warning in About Koha > System information about the encryption key missing - after enabling the TwoFactorAuthentication system preference, got to 'Manage two-factor authentication' for the koha user - you should get an error message pop up when trying to set up 2FA 2. If you try to add <encryption_key>__ENCRYPTION_KEY__</encryption_key> you will also get the warning and error message. 3. Changing __ENCRYPTION_KEY__ to something else will remove the warning and let you set up 2FA. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
