As per following 2 docs

SiteScope 11.93/11.94 - cacerts truststore password (microfocus.com)

Topology synchronization not working after upgrade - SiteScope (microfocus.com)

you should have look in  <SITESCOPE_DIR>\WEB-INF\classes\security   for ssl.properties  file. 

Hi,

I had come across those articles before, comparing the keystore password and truststore password in this file between working and not working
the passwords are the exact same.

I think that file more comes into play when using https (which we are not), it is just telling sitescope what the cacerts password is that is my issue.

Thanks,
Terry

One idea that may work... on the new cacerts change the password to the one that is in your upgraded sis. then copy over the file. This way SiS does not need to know new password as the coped over cacerts has the same password.

Hi,

Well on both installs I used the same password for changing the cacerts password as dictated by the install, but however I have no idea what the old pre-upgrade cacerts password used to be. I might try changing it to changeit which was the default and putting that truststore in but the install says changeit is no longer allowed.

There is a script file that changes keystore password  from SiteScope(it needs the old password). If you work it out you will know where it is checking and validating new password to the current password.

It is under <sis dir>/tools/Sitescopehardeningttool/  (please check the exact names as been a while)  the file name is something like runsslconfiguration.. 

(adding Ref:  Use the Hardening Tool - SiteScope (microfocus.com) )

Safer way would be to log a support call though as I am  sure there may be a support script or jmx call to do the same.

As a sideline here is the location of the sitescope cacerts password in case anyone else gets stuck.

Advice given was to create a new keystore etc....
"open file "<Sitescope>\tools\panel\toolbar.e1"
- find parameter _param8
- modify it to "_param8=changeit"
- incase not found param8 there, add the line "_param8=changeit" to the file
- save the change"

BUT that is all I needed.
The backups Sitescope creates backs up <Sitescope>\tools\panel\toolbar.e1 and <Sitescope>\tools\panel\toolbar.e3
So although the "upgrade" went OK when the backup was restored the old stored password in <Sitescope>\tools\panel\toolbar.e1 meant sitescope was using the wrong password.

To fix my issue I copied the cacerts from our development environment over.
I then edited <Sitescope>\tools\panel\toolbar.e1 in production and made sure _param8 matched the development value in the same file.
I recycled the Sitescope service and all is fine in the production instance for cacerts.