Werk #20211: mk_jolokia: Configure the verification of the server certificate in the agent rule
| Component | Agent bakery | ||||
| Title | mk_jolokia: Configure the verification of the server certificate in the agent rule | ||||
| Date | Sep 16, 2026 | ||||
| Level | Trivial Change | ||||
| Class | New Feature | ||||
| Compatibility | Compatible - no manual interaction needed | ||||
| Checkmk versions & editions |
|
The agent rule "JMX monitoring of Java JVMs using Jolokia (Linux, Windows)" allows connecting to the Jolokia server via HTTPS.
Previously, the rule offered no way to control how the certificate of the Jolokia server is verified.
If the CA of the server certificate was not trusted by the plug-in, the connection failed and the only way out was to edit jolokia.cfg manually on the monitored host.
The rule now offers the option "Verification of the server certificate", both for the default values and per instance. It provides the following choices:
- Use the certificate store of the monitored host (default). The certificate is verified against the CAs trusted by the monitored host, e.g. the Windows certificate store, and the CA bundle shipped with the Python
requestslibrary. - Use a CA file on the monitored host. Only the CA certificates in the given PEM file are trusted.
- Do not verify the server certificate. This is insecure and should only be used if the identity of the Jolokia server does not need to be verified.
Existing rules are not affected. Without the option set, the plug-in keeps its default behavior.