Title: haproxy: Adapted HAproxy Server State and HAproxy Frontend State rules to be item specific
Class: fix
Compatible: compat
Component: wato
Date: 1700826137
Edition: cre
Level: 1
Version: 2.2.0p16
HAproxy Server State and HAproxy Frontend State were not configurable with regard to the service name.
This means that the rules were applied to all services.
This has now been adapted and the rules can be configured to apply to certain services only.
Title: Keep label filters when sorting a view
Class: fix
Compatible: compat
Component: multisite
Date: 1700564389
Edition: cre
Level: 1
Version: 2.2.0p16
When a view was filtered for host/service labels and then sorted by clicking on one of the table headers, the label filters were lost.
This is fixed to conserving the label filters when sorting a view.
Title: mk_oracle: use "${GREP}" instead of "grep"
Class: fix
Compatible: compat
Component: checks
Date: 1701070131
Edition: cre
Level: 1
Version: 2.2.0p16
When executed on solaris, <code>"grep"</code> does not know <code>-x</code> or <code>-F</code>. "${GREP}" points
to a version of grep that understands those options.
Title: Browsing man pages from command line
Class: fix
Compatible: compat
Component: checks
Date: 1701023104
Edition: cre
Knowledge: undoc
Level: 1
State: unknown
Version: 2.2.0p16
Viewing a check plugins man page using <tt>cmk -M my_check</tt> left the terminal in a bad state.
Browsing man pages using <tt>cmk -m</tt> did not work at all (still leaving the terminal in a bad state).
This is fixed.
After running the commands <tt>cmk -M my_check</tt> or <tt>cmk -m</tt> the tty was not properly restored.
Affected users can fix their prompt running <tt>stty sane</tt> or <tt>restore</tt>.
Title: Introduce Last seen for the REST API usage
Class: feature
Compatible: compat
Component: wato
Date: 1700822001
Edition: cre
Level: 1
Version: 2.3.0b1
Prior to this Werk, the last time a REST API user was used was not
displayed in WATO and "Never logged in" was displayed. This Werk
changes the behavior and now displays the date and time of when it
was last used. These are the changes introduced in this Werk:
* Last seen column shows "Never" if the user was never authenticated.
* REST API users show the date and time when they last logged in.
* In the Act. column, the login icon includes the means by which
the authentication information was last received (bearer, cookie, etc.).
Title: primekey_hsm_battery_voltage: Fixed parsing of section when battery voltage is not available
Class: fix
Compatible: compat
Component: checks
Date: 1700831541
Edition: cre
Level: 1
Version: 2.3.0b1
Sometimes the battery voltage was not available or it wasn't a number. That cause the parsing of the section to fail.
This has now been fixed.
In the case of voltage being: 'External Battery: absence", the check status will be OK and the summary will provide details that the battery is absent.
If the voltage is not a number or is not absent, the voltage check will be skipped and the check result will the battery state.
Title: haproxy: Adapted HAproxy Server State and HAproxy Frontend State rules to be item specific
Class: fix
Compatible: compat
Component: wato
Date: 1700826137
Edition: cre
Level: 1
Version: 2.3.0b1
HAproxy Server State and HAproxy Frontend State were not configurable with regard to the service name.
This means that the rules were applied to all services.
This has now been adapted and the rules can be configured to apply to certain services only.
Title: Keep label filters when sorting a view
Class: fix
Compatible: compat
Component: multisite
Date: 1700564389
Edition: cre
Level: 1
Version: 2.3.0b1
When a view was filtered for host/service labels and then sorted by clicking on one of the table headers, the label filters were lost.
This is fixed to conserving the label filters when sorting a view.
Title: Deprecate automation user login via HTTP parameters
Class: feature
Compatible: compat
Component: wato
Date: 1700383158
Edition: cre
Level: 1
Version: 2.3.0b1
Checkmk offers a method to authenticate individual requests with the `_username`/`_secret` parameter.
This also works for GET requests and was used for the Webapi (removed in 2.2).
Having secrets in GET parameters is considered bad practice since these parameters are usually logged by webservers and web proxies.
With this Werk we deprecate this authentication method.
This means we now introduced a configuration option *Enable automation user authentication via HTTP parameters* to enable/disable this method.
By default it is enabled to not interrupt existing workflows.
In Checkmk 2.4 we will disable this by default so it will still be possible to enable this.
In Checkmk 2.5 this method will be removed entirely.
If you currently use this method we recommend to switch to Basic Authentication.
Title: Automationuser login must not open full session
Class: fix
Compatible: incomp
Component: wato
Date: 1700382222
Edition: cre
Knowledge: doc
Level: 1
Version: 2.3.0b1
Checkmk offers a method to authenticate single web requests with URL parameters (<tt>_username</tt> and <tt>_secret</tt>).
Due to some refactoring of the session handling with Checkmk 2.2 such automation requests initiated a full session.
The login for automation users was still blocked in the login screen but an authenticated request initiated a full session that could than be used to browse the Checkmk GUI like a regular user.
With this Werk that is no longer the case.
If you use this authentication method you should check if you rely on sessions for your automation users.