Built for ManageEngine
Pre-built templates for ADSelfService Plus, ADManager Plus, ADAudit Plus, and Endpoint Central ship in your CertKit account. No scripting required.
ManageEngine loads its HTTPS certificate when the Windows service starts. For ADSelfService Plus, ADManager Plus, and ADAudit Plus, that means replacing a keystore. Endpoint Central uses separate certificate and key files. With public certificate lifetimes heading to 47 days, that's more restarts to coordinate across every server.
CertKit renews the certificate. The CertKit Agent backs up the current files, installs the new certificate, restarts the product, and checks its HTTPS port.
Pre-built templates for ADSelfService Plus, ADManager Plus, ADAudit Plus, and Endpoint Central ship in your CertKit account. No scripting required.
On every renewal, the agent finds the product through its Windows service, backs up the current certificate files, installs the renewal, and restarts the service. If the HTTPS port fails verification, the agent restores the previous files and restarts the service again.
The restart takes the web console offline for a few minutes. For Endpoint Central, it can also interrupt agent communication. Use a deployment window to schedule the restart outside busy hours.
The manual process, if you want to do it yourself:
bin folder.
With public certificate lifetimes shrinking to 47 days, renewing a few weeks early means repeating this work about twelve times a year. If the ADSelfService Plus certificate expires, the people who need to reset their passwords may be the first to hit a certificate warning. An expired Endpoint Central certificate can interrupt mobile device management.
At 47 days, automation is the only sustainable way to run ManageEngine certificates. Here's how CertKit does it.
From an operational perspective, CertKit is easy to deploy and manage. The ability to configure unique and specialized certificates is key to replacing our manual certificate processes.
Laura Thomas, Senior Central Systems Administrator, University of St. Thomas
Your ManageEngine server CertKit ACME CA ┌───────────────────┐ ┌──────────────────┐ ┌─────────────┐ │ │ │ │ │ │ │ ┌───────────────┐ │ Issue & Renew │◄──►│ │ │ │ CertKit Agent ├──►│ Certificates │ │ │ │ └─────────┬─┬───┘ │ ┌───┐ └─────────────┘ │ │ │ │ └───────────┬────│DNS│ │ Keystore ◄──┘ │ │ │ └───┘ │ [x] Replaced │ │ │ │ │ │ │ │ ManageEngine◄───┘ │ ◄───────────────┘ │ [x] Restarted │ Verify └───────────────────┘
CertKit issues and renews certificates centrally using delegated DNS validation. You create a one-time CNAME record, and CertKit handles every ACME challenge after that.
The CertKit Agent runs on the ManageEngine server as Local System or an administrator. It pulls each renewal from CertKit over outbound HTTPS and installs it locally. The server never runs ACME, opens no ports, and holds no DNS credentials. CertKit never connects into your network.
Each product has its own certificate, so each has its own template. When several run on one server, add a deployment for each, and CertKit leaves the others alone.
server.xml looks. When Encrypt Keystore
Password hides that password, the agent sets a new one and writes it into the connector.
The AD products run on Tomcat, and the certificate is just a keystore file and a password
in server.xml. A scheduled task that copies a new PFX over it looks easy.
But once Encrypt Keystore Password is on, the password is encrypted in the product's
database, so the script doesn't know what to protect the new keystore with. Get it wrong
and the product starts with no HTTPS at all. An ECC certificate fails the same way when the
connector's cipher list has no ECDSA suites.
CertKit checks the connector's password and cipher settings before changing the keystore. If the new certificate fails the HTTPS check after restart, the agent attempts to restore the previous keystore and CertKit alerts you.
Most Windows environments have more than one place where certificates live: identity services like AD FS, mail on Exchange, other Tomcat-based apps like Apache Tomcat itself, and web servers like IIS. CertKit automates all of it from one account, and issues from your Active Directory Certificate Services root for the internal names a public CA will not sign.
Free 30-day trial. No credit card required. Direct access to our engineering team to get you set up.