Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

WPM is still using old SHA1 certificate after the 2023.2 upgrade

Hi Team,

I have noticed that after upgrading to 2023.1 and next to 2023.2, I still have old SHA1 certificate for WPM Playback. This could be a potential security issue.

Below release notes for WPM 2023.1 include new certificate:

https://documentation.solarwinds.com/en/success_center/wpm/content/release_notes/wpm_2023-1_release_notes.htm

"WPM SSL Certificate is now signed using SHA256 encryption algorithm or higher."

I have manually removed it from Certificate Authority and ran Configuration Wizard. This resolved my problem and now I have SHA512 certificate:

However, this should be replace during the upgrade process. I hope this helps you and SolarWinds will correct the installer

Take care, Marcin.

Update: As per discussion in comments, as an alternative solution, you could delete the certificate and restart the machine. New certificate will be created without running Configuration Wizard.

Find more posts tagged with

Accepted answers

All comments

jvb

Thanks @kpmarcin I will ask the engineering team to look into this.

michal.kalina

Hi, have you tried to remove the old certificate with SHA1 and restarted the WPM Player service? WPM Player will not create a certificate if there is already 'SolarWinds-SEUM_PlaybackAgent' certificate in the store.

kpmarcin

Hi @michal.kalina

I have done a snaphot of my main poller before doing those steps, so I restored it and tried your suggestion. I removed the certificate and restarted all WPM services. The certificate was not recreated. Next, I restarted Windows Server and certificate was recreated. So, there is an option to repair it without Configuration Wizard, but it would require a reboot. Thanks, I will include this in my post, as an alternative option.