Sectigo Certificate Manager release 20.9


Sectigo nos ha enviado un mensaje indicando que va a actualizar SCM a la versión 20.9. El mensaje dice lo siguiente:

Title: Sectigo Certificate Manager release 20.9 Scheduled Maintenance for Saturday, October 3, 2020, 12:00 PM UTC

Planned Start: October 3, 2020 12:00PM UTC
Expected End: October 3, 2020 6:00PM UTC

Affected Infrastructur
Components: Management Platforms
Locations: SCM (,SCM (


Sectigo Certificate Manager release 20.9 Scheduled Maintenance for Saturday, October 3, 2020, 12:00 PM UTC

The SCM 20.9 release includes the following enhancements and fixes:

  • SCM-2415 - Updated user interface for customer admins and self-service endpoints to better match Sectigo's corporate look and feel.
  • SCM-2327 - Existing ACME configuration moved to the new Enrollment Endpoints section in settings.
  • SCM-2328 - New ACME endpoint added that supports certificate issuance via Private CA backend.
  • SCM-2390 - Delegation of a certificate profile to an organization (or department) can now be canceled from the organization (or department) editor.
  • SCM-2455 - New REST API request parameter to specify the term for device certificate enrollment requests.
  • SCM-2117 - SCM Trial account automatically configured with Private CA backend.
  • SCM-2032/SCM-2399 - New download format to support SSL certificate before issuer certificates without the root certificate.
  • SCM-2434 - Improvements to REST/SOAP API and bulk CSV format to allow the setting of all fields for a person.
  • SCM-2236 - Improvements to the REST API to allow setting external requester, comments, and custom fields of an issued certificate.
  • SCM-1882/SCM-2688 - The ability to remove individual fields when requesting an SSL certificate via the UI or from a client certificate when performing self-enrollment has been removed. The Subject of a certificate can now be customized in the certificate profile so that all enrollment endpoints work the same.
  • SCM-2389 - Newly created department now automatically inherits the certificate profiles delegated to an organization it belongs to.
  • SCM-1605/SCM-2379 - More informative error messages.
  • SCM-2256 - Improved tooltips on the notification editor.
  • SCM-2561 - No more automatic selection of the only available term in the certificate profile editor if the only enabled term becomes unavailable. This caused confusion since it seemed like the profile was correct when it wasn't.
  • SCM-2446 - Improved handling of deleted certificate template or profile. Certificates from the deleted profile cannot be renewed or replaced but can be revoked.
  • SCM-2283/SCM-2315 - Requesting an SSL certificate through REST/SOAP API when enrollment backend was unavailable might return an error, however, the request was successfully submitted. The request would be applied once the backend is available.
  • SCM-2410 - Incorrect error code returned when a request for a publicly trusted client certificate through SOAP API failed due to a non-validated domain. (-116 instead of -25 error code)
  • SCM-1921 - Adding a new server before the running "Discover Target Servers" command was completed caused the deletion of this server from UI.
  • SCM-2467 - RAO Administrator could not create a department through REST API.
  • SCM-2582 - Download of device certificate with a comma in the CN fails on Google Chrome browser.
  • SCM-2221/SCM-2535/SCM-2405 - A few SSL certificates could not be renewed, replaced, or revoked after deployment of SCM 20.5.
  • SCM-1597 - Incorrect certificate revocation date shown in some cases.
  • SCM-1597 - The server is shown as inactive when some an https node is misconfigured.
  • SCM-1115 - Auto-installation of a certificate failed if the Run Between times are too close together.
  • SCM-2104 - Certificate replacement used old EV details instead of current values from the organization.
  • SCM-2595 - Domains may not be listed when creating an ACME account if the browser time zone is ahead of UTC.
  • SCM-2303 - SSL enrollment via the self-enrollment portal failed when the configured custom fields contained specific characters.