Quote:
Originally Posted by mjeanson Turns out my certificate files were missing newline character on the last line which caused openssl to not recognise the concatenated file that contained the certificate and the CA. |
If you'll allow me to translate (because it took me an hour to figure out exactly what this comment meant):
Behind the scenes, the process that the admin tool uses to import your certificates is the same as the suggested manual procedure: it puts files into magic places under the webapps directory, then runs zmcertmgr to deploy the certificate.
However, that tool concatenates together whatever your supplied for commercial.crt and whatever you supplied for ca.crt. If there aren't linefeeds at either the end of commercial.crt or the beginning of ca.crt, then the process that makes jetty's pkcs12 file doesn't recognize the merged certs as being valid. So you have to make sure those files that you're uploading do have some extra linefeeds at the top and bottom.
It seems to me that zmcertmgr and/or the admin tool could do this
for you. Barring that, there could at least have been a straight answer somewhere on the wiki, or the forums, or in the documentation. I just spent two damned hours fixing this problem.