[BUG] Updating Ubuntu JSS with 8.71 destroyed my .jks certificate

[justinrummel]

Just warning others who may have purchased a 3rd party certificate. This may be VERY specific to my install so it may not apply to everyone.

My 3rd party signed certificate in Ubuntu Server in /usr/local/jss/tomcat/ and was running 8.63. I ran the Linux 8.71 installer, and after it was finished the service would not restart.

Checked my catalina logs and found this line:
[code]SEVERE: Failed to load keystore type JKS with path /usr/local/jss/tomcat/auto.rummel.co.jks due to /usr/local/jss/tomcat/auto.rummel.co.jks (No such file or directory)[/code]

Confirmed the file was missing. Luckily I COPY my cert from the admin home directory vs. move. Just recopied the .jks file to the same location, sudo service jamf.tomcat7 restart and things are now back up and running.

[jarednichols]

I'm not so sure that this is a bug vs expected behavior. I was under the assumption that anything in your tomcat directories is pretty much fair game to get hosed during an upgrade - thus why I always backed up my server.xml file and .keystore file. Though I never saw my .keystore file get hosed, the server.xml file got hosed plenty. I wonder if you having a .jks vs a .keystore has anything to do with it.

[dokihara]

my P12 keystore was still there after I Updated from 8.62 to 8.71 on OS X server. I had to redo my server.xml file.