Werk #22709: Fix password changes not reaching the monitoring core
| Component | Setup | ||||
| Title | Fix password changes not reaching the monitoring core | ||||
| Date | Oct 12, 2026 | ||||
| Level | Prominent Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Compatible - no manual interaction needed | ||||
| Checkmk versions & editions |
|
This werk affects Checkmk Community and Checkmk Cloud.
Since 2.5.0, adding, editing or deleting a password anywhere in Setup or through the REST API did not update the monitoring core's configuration. On the site where you made the change, Checkmk did not even list it as pending, so there was nothing to activate. Active checks, special agents and, in Checkmk Cloud, relays and the agent bakery kept using the old password until another change made Checkmk regenerate the core configuration.
Password changes are pending changes again, and Activate changes updates the core. Updating to this version regenerates the core configuration, so on the site where you changed a password before the update it takes effect as well. Remote sites of a distributed setup receive such a password only with the next activation that synchronizes them. To push it right away, save the password again after the update and activate the change.