Applications Systems

SAM: Issues due to revoked code-signing certificates

We have made the decision to digitally re-sign SAM; the existing certificate is currently scheduled to be revoked on March 8, 2021. Installation of affected versions of SAM may be forbidden by system policy. This article describes steps to address the possible issues in SAM.

First published date

12/22/2020 2:03 AM

Last published date

1/25/2021 6:06 AM

Overview

As a best practice and to further enhance the security of our products, we have retained third-party cybersecurity experts to assist us in these matters. These experts are guiding us in improving our processes and controls.  

To that end and to provide additional assurance to all of our customers, we made the decision to digitally re-sign our products and have requested (and received) a new digital certificate. This reflects a recertification of the authenticity of SolarWinds products, both current and future.  


What to expect next: 
  • We will be issuing new product release for SAM containing the updated certificate.
  • The existing certificate is currently scheduled to be revoked on March 8, 2021.

If they fail to upgrade to the newest version, SAM users might notice the following issues: 
  • Existing users cannot start affected versions of SAM.
  • New users cannot install affected versions of SAM.

A complete list of affected versions includes:
  • SAM 2020.2
  • SAM 2020.2 HF1
  • SAM 2020.2.1
  • SAM 2020.2.1 HF1

Product section

Server Application Monitor

Cause

Revoked code-signing certificates

Resolution

If SAM users experience any of these issues, SolarWinds strongly recommends upgrading to the latest available version.  For details, see the Orion Platform Products Installation and Upgrade Guide.

If these issues persist, contact Support.