my builds continue as usual and even though the jar signing logs now say the cert is expired, the build and jar signing passes and the JNLP file can be launched with no issues, no prompts or anything. everythinkg seems to magically keep on working. its like no one cares that the code signing cert has expired
can someone explain this? i would expect the build to fail and/or the browser/ows runtime to reject the jar downloading due to the fact they arent signed with a valid cert... i am confused. any comments would be appreciated. thanks.
here is a log output from jar signing of a single jar (there are more like this):
[signjar] The signer certificate expired on 2024-03-09. However, the JAR will be valid until the timestamp expires on 2031-11-10.
[signjar] jar signed.