diff --git a/admin_manual/release_notes/upgrade_to_30.rst b/admin_manual/release_notes/upgrade_to_30.rst index f1b7fe0cf54..bac50772d2d 100644 --- a/admin_manual/release_notes/upgrade_to_30.rst +++ b/admin_manual/release_notes/upgrade_to_30.rst @@ -36,3 +36,8 @@ Automated clean-up of app password ---------------------------------- Nextcloud 30 will :ref:`clean-up unused app passwords`. + +Monitoring: Counting of active users +------------------------------------ + +Starting with Nextcloud 30.0.12 the monitoring app was adjusted to count the active users in the same way as occ user:report and the support app. diff --git a/admin_manual/release_notes/upgrade_to_31.rst b/admin_manual/release_notes/upgrade_to_31.rst index 0921abce581..ce00d4e6f5f 100644 --- a/admin_manual/release_notes/upgrade_to_31.rst +++ b/admin_manual/release_notes/upgrade_to_31.rst @@ -38,3 +38,8 @@ Previously it was set to 10MiB, it is now increased to 100MiB. Also the configuration was moved from an app configuration to the system configuration (``config.php``). If you set up a custom value previously the value will be automatically migrated to the system configuration during the update. But if you need to set a new custom value you need now to use the system configuration, see also :ref:`files_configure_max_chunk_size`. + +Monitoring: Counting of active users +------------------------------------ + +Starting with Nextcloud 31.0.6 the monitoring app was adjusted to count the active users in the same way as occ user:report and the support app. \ No newline at end of file diff --git a/admin_manual/release_notes/upgrade_to_32.rst b/admin_manual/release_notes/upgrade_to_32.rst index 22893b0e8ac..d4154f93d17 100644 --- a/admin_manual/release_notes/upgrade_to_32.rst +++ b/admin_manual/release_notes/upgrade_to_32.rst @@ -14,3 +14,8 @@ Web server configuration * Setup checks do not check for the ``X-XSS-Protection`` response header anymore. It has been removed from Nextcloud's ``.htaccess`` and you may want to adjust your webserver config to not serve it anymore. XSS filtering was supported only until Chromium 78 and similarly old browsers, but had been found to cause more issues, including attack vectors, than it solved. Nowadays, aside of not serving the header at all, the only generally recommended value is ``0``. More context can be found in the `OWASP Cheat Sheet Series `_. + +Monitoring: Counting of active users +------------------------------------ + +The monitoring app was adjusted to count the active users in the same way as occ user:report and the support app. \ No newline at end of file