Certificate validation and enabling all trusts

Beginning with RtReports 5.1, AVEVA has changed the default Server Certificate Validation to improve security. If the server’s certificate cannot be validated, the editor cannot be accessed and the loading of certain data from unverified sources during PDF generation will be blocked. This change is intentional, and AVEVA strongly advises against bypassing it. If your RtReports installation is using a certificate that cannot be validated, please consult your company’s IT Team for guidelines around generating and managing certificates.

To resolve certificate issues, you can renew existing expired trusted certificates or create new certificates and add them to your machine’s or domain’s trusted root authority. Any change to the certificate will require an Internet Information Services (IIS) restart.

AVEVA discourages disabling certificate validation entirely. If you choose to bypass certificate validation, you must set the value of EnableTrustAllCertificates to true in all the following files:

• %PIHOME%\RtReports\OSISoft.RtReports.Editor.exe.config

• %PIHOME%\RtReports\bin\OSISoft.RtReports.RtRemotingHost.exe.config

• %PIHOME%\RtReports\web.config

Changing this setting in only some files can lead to unexpected results. After making these changes, restart IIS to apply them.