Skip to content

Manage certificates

Certificate-based security ensures secure communication and reliable authentication within Octoplant environments. By default, Octoplant automatically creates a self-signed certificate and private key at runtime.

Custom certificate management

To meet organizational or regulatory requirements, such as integrating identity providers like Azure AD, you can replace the default certificate with one issued by a trusted Certificate Authority (CA).

If you use the WebClient, replacing the self-signed certificate is strongly recommended to avoid browser trust warnings.

Troubleshoot certificate issues

Even with a trusted CA certificate, warnings may occur for the following reasons:

  • Missing CA in the browser’s trusted store, which is common on older systems: Keep systems updated to receive new CA certificates through Windows Update.
  • Missing intermediate certificates: Make sure that your server provides the full certificate chain, including intermediate and root certificates.
  • Expired certificate: Renew or replace the certificate as needed.

See Configure trusted root certificates if you encounter certificate issues when the Octoplant server tries to establish communication with external sites, such as myAMDT, Octoplant Pro Hub, or Octovision.

Contact your IT department to address certificate issues.

Related topics