Request to use a certificate thumbprint for scheduled reports when SSL is enabled.
Background:
We use scheduled reports, but we recently enabled SSL which broke the process. The exporttopdfcmd.exe, which runs the reports, currently uses a file path to the certificate which allows the scheduled reports to work with SSL enabled. This however presents a vulnerability as the certificate cannot be stored on the server. We can't leave it there, and the only solution we could come up with is if the exporttopdfcmd.exe could use the certificate thumbprint instead of a file path to the .p12 file.
The use of a certificate thumbprint would eliminate the need to store the .p12 file on the server, but a workaround is not currently available per SolarWinds support. Case number 01955880. The rep opened a development case which is internal to SolarWinds. I have placed this request to gather votes from community members who may be facing similar issues.