Werk #18761: Site connections: Reject site IDs that cannot be an OMD site name
| Component | Setup | ||||
| Title | Site connections: Reject site IDs that cannot be an OMD site name | ||||
| Date | Aug 13, 2026 | ||||
| Level | Trivial Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Incompatible - Manual interaction might be required | ||||
| Checkmk versions & editions |
|
A site connection could be created with an ID that no site can ever have. omd
create accepts a site name only if it begins with a letter or underscore,
consists of letters, digits and underscores, and is at most 16 characters long.
The Setup GUI and the REST API were more permissive: both accepted dashes and
arbitrarily long IDs, and the REST API also accepted a leading digit.
Such a connection cannot refer to a real site. It also broke unrelated functionality: every quick setup offering a site selection (Amazon Web Services, Microsoft Azure, Google Cloud Platform, Proxmox VE) raised an exception as soon as one configured site ID was not a valid identifier, because the site IDs are used as the keys of the selection.
Creating a site connection now applies the same rule as omd create, in the
Setup GUI as well as in the REST API. Requests that used to succeed with such an
ID now fail with an error naming the rule.
Existing site connections are not affected: their ID is validated neither on editing nor on activation, so they keep working as before. A site connection whose ID was created under the old rule will however still make the quick setups mentioned above fail. Delete such a connection and create it again with an ID that matches the name of the site it connects to.