6.5.35 ManageEngine

Run the agent on the ManageEngine server, turn on HTTPS first, and expect a restart

CertKit has one template for each ManageEngine product. Each installs the certificate as the product’s HTTPS certificate, restarts the product’s Windows service, and checks that the HTTPS port serves the new certificate. If it doesn’t, the template puts the previous files back and restarts the product again.

Template What it replaces Format
ManageEngine ADSelfService Plus The keystore named in conf\server.xml PFX
ManageEngine ADManager Plus The keystore named in conf\server.xml PFX
ManageEngine ADAudit Plus The keystore named in conf\server.xml, also used by the agent port (8555) PFX
ManageEngine Endpoint Central server.crt, server.key, and the intermediate file in the web server’s conf folders PEM cert + key + separate chain

When several products run on one server, add a deployment for each. Each template leaves the other products alone.

Requirements

  • Install the CertKit agent on the ManageEngine server itself.
  • Run the agent as Local System or an administrator, so it can write to the install folder and restart the service.
  • The product must run as a Windows service, not in console mode, and be running when the deployment starts.
  • There’s nothing to fill in. The install folder, keystore, and HTTPS port are found from the Windows service.

The web console is unavailable for a few minutes during the restart. Use a deployment window.

ADSelfService Plus, ADManager Plus, and ADAudit Plus

Turn on HTTPS in the product first, under Admin > Product Settings > Connection in ADSelfService Plus or Admin > General Settings > Connection in ADManager Plus and ADAudit Plus. The template doesn’t switch HTTPS on or change ports.

The template builds a new keystore with the CertKit certificate and writes it where the HTTPS connector already looks. It protects the keystore with the password in server.xml. When Encrypt Keystore Password is on, that password is encrypted in the product’s database, so the template sets a new keystore password and writes it into server.xml.

ADManager Plus and ADAudit Plus have a Keystore password setting. Leave it on auto. Set it only to keep Encrypt Keystore Password in use, by entering the password of the certificate file you last uploaded in the product’s SSL Certificate Tool.

Key types

ADSelfService Plus works with RSA and ECC certificates. ADManager Plus and ADAudit Plus serve ECC certificates only after you add ECDSA ciphers under Admin > Connection. When the connector’s cipher list has no ECDSA suites, the template stops before changing anything.

High availability

Each server in a high availability pair keeps its own keystore and has to restart to load it. Install the agent on both servers, add the template on each, and give them different deployment windows so they don’t restart at the same time. A passive standby that doesn’t answer on HTTPS is updated too and reported as installed, not verified.

Endpoint Central

Before the first deployment, import your certificate once in the web console under Admin > Security Settings > Manage SSL Certificate. That first import is where Endpoint Central moves its agents off its built-in certificate. The template stops if the server still uses the built-in certificate.

Keep the same host name on the certificate that your agents use to reach the server, under Admin > NAT Settings. Agents check it.

ManageEngine supports RSA keys only on Endpoint Central. If your certificate authority changes to one with a different root, follow ManageEngine’s steps to reconfigure the Secure Gateway Server afterward.

Backups and rollback

Before each change, the template copies the files it replaces to <name>.certkit-backup-<timestamp> in the same folder and keeps the newest three. If the restart or the HTTPS check fails, it copies the backups back and restarts the product. The backups contain private keys, so restrict access to the folder.

Common problems

  • “No … Windows service was found on this machine”: run the template on the ManageEngine server, with the product installed as a Windows service.
  • “HTTPS is not switched on”: turn on HTTPS in the product’s connection settings, restart it once, and deploy again.
  • “This is an ECC certificate, but the cipher list … only allows RSA certificates”: use an RSA certificate, or add ECDHE_ECDSA ciphers in the product.
  • “The keystorePassword variable does not match”: set Keystore password back to auto.
  • “This template supports JKS and PKCS12 keystores only”: FIPS mode uses a BCFKS keystore, which the template doesn’t support.
  • “This server still uses Endpoint Central’s built-in certificate”: import your certificate once in the web console, then deploy again.
  • “After the restart … did not answer on HTTPS port”: the product didn’t come back in time. The template restored the previous files. Check the product’s logs.

For a product overview, see certificate automation for ManageEngine.