Branch: refs/heads/2.0.0
Home:
https://github.com/tribe29/checkmk
Commit: 0327c73263d290ebb22caaae35e112519fb23208
https://github.com/tribe29/checkmk/commit/0327c73263d290ebb22caaae35e112519…
Author: Sven Panne <sven.panne(a)tribe29.com>
Date: 2023-02-06 (Mon, 06 Feb 2023)
Changed paths:
A .werks/15252
Log Message:
-----------
15252 FIX Fixed "processing of perfdata" condition
The logic for the processing of performance data was broken: It should only
be done when the global switch is activated <em>and</em> the processing is
enabled for the host/service in question. The condition was incorrectly
using an "or" for this, this has been fixed.
Change-Id: Ia900205464fbedd09160e7f5ee95ba9986b06d93
Commit: c8406e28af9a1bb8e787dbfd6814dac4558cb40d
https://github.com/tribe29/checkmk/commit/c8406e28af9a1bb8e787dbfd6814dac45…
Author: Hannes Rantzsch <hannes.rantzsch(a)tribe29.com>
Date: 2023-02-06 (Mon, 06 Feb 2023)
Changed paths:
A .werks/15187
M cmk/gui/plugins/openapi/endpoints/user_config.py
M cmk/gui/wato/pages/users.py
M cmk/gui/watolib/users.py
Log Message:
-----------
15187 FIX Enforce password policy in REST API and user management
Prior to this Werk both the REST API and the user management UI (Setup > Users) did not
correctly enforce the password policy for local accounts.
As a result, administrators with the "User management" permission could set
passwords that don't comply with the policy for their own or other users'
accounts.
Note that the "Change password" option in the user profile menu was not affected
by the issue and correctly checked the password policy.
Change-Id: I24ef58dddb8142ac83cb113ec69b55570c5d83e7
Compare:
https://github.com/tribe29/checkmk/compare/520b080736a1...c8406e28af9a