After installing a new SSL certificate and running Reconfigure, the log shows a line about creating the keystore, but the actual `ifsKeystore.jks` file under the OHS instance's keystores folder never gets updated or regenerated — even after renaming/removing the old file and rerunning Reconfigure.

Q: After installing a new SSL certificate and running Reconfigure, the log shows a line about creating the keystore, but the actual `ifsKeystore.jks` file under the OHS instance's keystores folder never gets updated or regenerated — even after renaming/removing the old file and rerunning Reconfigure.

Reconfigure only generates a new ifsKeystore.jks when it's given a new, differently-named source .pfx certificate file to import — renaming or deleting the existing .jks file alone doesn't trigger regeneration, since Reconfigure keys off the .pfx filename rather than the presence/absence of the .jks output file. Give your new certificate's .pfx file a new/different filename from whatever was used previously, then rerun Reconfigure — this causes a fresh keystore file to actually be created in the expected keystore folder.

Answer

Reconfigure only generates a new ifsKeystore.jks when it's given a new, differently-named source .pfx certificate file to import — renaming or deleting the existing .jks file alone doesn't trigger regeneration, since Reconfigure keys off the .pfx filename rather than the presence/absence of the .jks output file. Give your new certificate's .pfx file a new/different filename from whatever was used previously, then rerun Reconfigure — this causes a fresh keystore file to actually be created in the expected keystore folder.

← Browse Developer Studio, deployment, and upgrades questions