Werk #22385: Refuse to delete a customer that passwords, BI or Event Console objects still use
| Component | Setup | ||||||
| Title | Refuse to delete a customer that passwords, BI or Event Console objects still use | ||||||
| Date | Oct 6, 2026 | ||||||
| Level | Trivial Change | ||||||
| Class | Bug Fix | ||||||
| Compatibility | Compatible - no manual interaction needed | ||||||
| Checkmk versions & editions |
|
Werk #22140 stopped you from deleting a customer that groups, users or LDAP/SAML connections were still assigned to. Several other objects can be assigned to a customer too, and Checkmk ignored them:
- Passwords (Setup > General > Passwords)
- BI aggregations
- Event Console rule packs and rules
After you deleted the customer, these objects were left pointing to a customer that no longer existed.
Checkmk now refuses to delete a customer while any of these objects are still assigned to it. As with the objects from werk #22140, the page Setup > Users > Customers lists them with a link to their edit page, and the REST API endpoint for deleting a customer returns status 409 and names them.