ID: 13413
Title: cisco_cpu_multiitem: remove unsupported CPUs
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Before this change a Service <tt>CPU utilization 0</tt> was created, although
the corresponding MIB describes that <tt>0</tt> for cpmCPUTotalPhysicalIndex
indicates that this element is not supported.
Those Services will no longer be discovered.
ID: 12704
Title: Do not create Carbon data if no connection is configured
Component: Core & setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
The core would create and enqueue data for the Carbon connection
even if none is configured. This may incur a small performance
penalty and, provided the site generates a large amount of data,
log messages such as
<tt>[carbon connection pool] queue full, didn't push update</tt>
that are irrelevant.
This fix only sends data to the Carbon connection if necessary.
ID: 13412
Title: Update manpage for check 'seh_ports'
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
This check shows the state of the ports of the SEH myUTN dongle server
devices. The state of the port is not interpreted by checkmk, only displayed.
It is always shown as OK, except when the state changes:
If the current port state differs from the state seen at service discovery
time, the service will report WARN. To acknowledge the changed port, execute
the service discovery again.
ID: 13806
Title: API: addition of option to configure interface related attributes for user endpoints
Component: REST API
Level: 1
Class: New feature
Version: 2.2.0i1
This werk introduces the possibility to configure interface related attributes
for the user during the creation and update process. The options are described
under the following endpoints:
* Create an user
* Edit an user
The options are set by default for the create endpoint.
ID: 13674
Title: Fix usage of system wide CAs after update
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
On update to 2.1.0b1, the configuration setting "Trusted certificate
authorities for SSL" - "Use system wide CAs" was set to false, leading to
different problems with intergrations that used TLS.
ID: 13655
Title: REST API host_config: fix the create and update endpoints when including a host attribute
Component: REST API
Level: 1
Class: Bug fix
Version: 2.2.0i1
In the previous version, the create and update host endpoints returned
a 500 error when the user tried to register or modify a host with attributes.
This werk fixes this behaviour and returns a 400 error when an invalid
attribute is included.
ID: 13768
Title: API: addition of enforce password change as configurable option for user create endpoint and moving the option in for the update endpoint
Component: REST API
Level: 1
Class: New feature
Version: 2.2.0i1
In the previous version, the enforce_password_change option was always set to True
when creating a new user with a password and was not a configurable option. This werk
changes this and introduces this as a configurable option defaulting to False. In
addition, this werk also moves this option to the auth password details for the update endpoint.
ID: 13767
Title: API: fix show all users endpoint call when users have no emails
Component: REST API
Level: 1
Class: Bug fix
Version: 2.2.0i1
In the previous version, the show all users endpoint returned an error
if one of the users had no email present in its contact information.
This werk fixes this behaviour. It should be noted that this case is only
relevant for internal users. Users created through the REST-API or the UI
will always have an email placeholder field even if an email was not
specified.
ID: 13651
Title: API: fix user config show endpoints to include user attributes
Component: REST API
Level: 1
Class: Bug fix
Version: 2.1.0i1
In the previous version, both the show user and show all users
endpoints did not behave as intended hiding the user attributes.
This werk changes this behaviour and also introduces proper field
definitions for the response schema. The response of the user
endpoint has also changed. Every attribute which was previously
returned under "extensions.attributes", will now be returned
directly under "extensions". You may have to change your scripts
accordingly. The affected endpoints are:
*/objects/user_config/user (get & put)
*/domain-types/user_config/collections/all (get & post)