Using a Trusted Certificate

Everpure Cloud Azure Native

Audience
Public
Source Type
Documentation

By default the Platform Console management endpoint presents a self-signed certificate, so browsers show a certificate warning on first access. Customers who require a trusted connection should upload a certificate signed by their own certificate authority. Both direct upload of a certificate and a certificate signing request flow are supported through the Platform Console GUI or REST API.

The uploaded certificate applies only to the customer-facing management endpoint. Internal certificates used by the managed service are separate and are not affected. Because the certificate is uploaded through the management endpoint itself, the first upload necessarily takes place before a trusted certificate is in position; customers who want to avoid trusting the self-signed certificate at any point can perform the initial upload over CLI instead of the browser. Certificate upload through Azure is not available.