openITCOCKPIT version 4.5.1 has been released.
The openITCOCKPIT 4.5.0 we introduced a major change to the permissions of host groups. This change was done, because of a paradox which the user permissions. If you add a Host from a sub-container to a host group which is located in the Root-Container, you are changing the host group object. This would require write permissions to the Root-Container.
We addressed this issue with openITCOCKPIT 4.5.0. Unfortunately this change caused massive side effect so we decided to rollback the old behavior.
We also resolved an bug, there the form for editing hosts did not display all available hostgroups due to the paradox permissions.
We apologize for the inconvenience caused.
openITCOCKPIT version 4.5.0 has been released. Among other features are some major changes to the container permissions of host groups.
In versions prior 4.5.0, it was possible to assign hosts from the Root-Container, to a host group outside of the Root-Container. This leads to an inconsistent configuration state as soon as a user edits the configuration of a host. The form for editing hosts, will only show host groups, which are in the same container (or sub-container) as the host itself. This behavior is also adopted for the host group masks as well.
The brand new openITCOCKPIT Mobile website for Enterprise Edition users gives you an overview for your monitored devices at a glance – from everywhere! It is explicitly developed for Mobile devices.
openITCOCKPIT Mobile is deployed via Docker and can be hosted separately from openITCOCKPIT. It uses the openITCOCKPIT API with the API Key Authentication. To make things easier, we have integrated a new functionality in openITCOCKPIT, which allows you to scan the API Key as QR-Code.
openITCOCKPIT version 4.4.0 has been released. It is packed with new features and improvements like: Support for LDAP groups, the ability to use the openITCOCKPIT Monitoring Agent via satellite systems and automatically check deployment using the Import Module.
openITCOCKPIT distinguishes between two options to define user permissions: